PR #111023 pull-kubernetes-e2e-capz-windows-containerd #1591094625962037248
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | pohly: dynamic resource allocation |
| Result | FAILURE |
| Tests | 1 failed / 0 succeeded |
| Started | |
| Elapsed | 1h7m |
| Revision | a2d73b31f69b391e5bf1bd9ef8e2e654d1b101c1 |
| Refs |
111023 |
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 | 0xc000b4eb28>: {
error: <*errors.withMessage | 0xc00050caa0>{
cause: <*errors.errorString | 0xc000ece9f0>{
s: "error container run failed with exit code 1",
},
msg: "Unable to run conformance tests",
},
stack: [0x2eef258, 0x32e7387, 0x1876cf7, 0x32e7153, 0x14384c5, 0x14379bc, 0x187855c, 0x1879571, 0x1878f65, 0x18785fb, 0x187e889, 0x187e272, 0x188ab71, 0x188a896, 0x1889ee5, 0x188c5a5, 0x1899e09, 0x1899c1e, 0x32ec2f8, 0x148dc2b, 0x13c57e1],
}
Unable to run conformance tests: error container run failed with exit code 1
occurred
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:232
[BeforeEach] Conformance Tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:55
INFO: Cluster name is capz-conf-whcdvl
�[1mSTEP�[0m: Creating namespace "capz-conf-whcdvl" for hosting the cluster
Nov 11 16:20:38.739: INFO: starting to create namespace for hosting the "capz-conf-whcdvl" test spec
INFO: Creating namespace capz-conf-whcdvl
INFO: Creating event watcher for namespace "capz-conf-whcdvl"
[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-whcdvl" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.26.0-beta.0.15+cc704f97784c33, 1 control-plane machines, 0 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-conf-whcdvl --infrastructure (default) --kubernetes-version v1.26.0-beta.0.15+cc704f97784c33 --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-whcdvl/capz-conf-whcdvl-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-whcdvl/capz-conf-whcdvl-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-whcdvl-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-whcdvl-md-win are in the "<None>" failure domain
INFO: Waiting for the machine pools to be provisioned
INFO: Using repo-list '' for version 'v1.26.0-beta.0.15+cc704f97784c33'
�[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" "--" "--kubeconfig=/tmp/kubeconfig" "--provider=skeleton" "--report-dir=/output" "--e2e-output-dir=/output/e2e-output" "--dump-logs-on-failure=false" "--report-prefix=kubetest." "--num-nodes=2" "-dump-logs-on-failure=true" "-ginkgo.flakeAttempts=0" "-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" "-prepull-images=true" "-disable-log-dump=true" "-ginkgo.progress=true" "-ginkgo.slow-spec-threshold=120s" "-ginkgo.timeout=3h" "-ginkgo.trace=true" "-ginkgo.v=true" "-node-os-distro=windows"]
Running Suite: Kubernetes e2e suite - /usr/local/bin
====================================================
Random Seed: �[1m1668184234�[0m - will randomize all specs
Will run �[1m339�[0m of �[1m6812�[0m specs
Running in parallel across �[1m4�[0m processes
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.863 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:76�[0m
�[38;5;243mBegin Captured GinkgoWriter Output >>�[0m
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:76
Nov 11 16:30:34.507: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 11 16:30:34.509: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 11 16:30:35.013: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 11 16:30:35.411: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:35.411: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:35.411: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:35.411: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 11 16:30:35.411: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:35.411: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:35.411: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:35.411: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:35.411: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:35.411: INFO:
Nov 11 16:30:37.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:37.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:37.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:37.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 11 16:30:37.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:37.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:37.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:37.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:37.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:37.805: INFO:
Nov 11 16:30:39.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:39.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:39.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:39.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 11 16:30:39.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:39.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:39.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:39.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:39.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:39.806: INFO:
Nov 11 16:30:41.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:41.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:41.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:41.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 11 16:30:41.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:41.819: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:41.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:41.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:41.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:41.819: INFO:
Nov 11 16:30:43.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:43.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:43.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:43.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 11 16:30:43.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:43.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:43.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:43.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:43.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:43.806: INFO:
Nov 11 16:30:45.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:45.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:45.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:45.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 11 16:30:45.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:45.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:45.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:45.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:45.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:45.805: INFO:
Nov 11 16:30:47.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:47.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:47.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:47.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 11 16:30:47.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:47.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:47.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:47.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:47.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:47.805: INFO:
Nov 11 16:30:49.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:49.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:49.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:49.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 11 16:30:49.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:49.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:49.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:49.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:49.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:49.805: INFO:
Nov 11 16:30:51.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:51.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:51.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:51.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 11 16:30:51.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:51.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:51.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:51.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:51.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:51.810: INFO:
Nov 11 16:30:53.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:53.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:53.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:53.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 11 16:30:53.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:53.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:53.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:53.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:53.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:53.804: INFO:
Nov 11 16:30:55.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:55.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:55.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:55.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 11 16:30:55.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:55.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:55.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:55.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:55.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:55.806: INFO:
Nov 11 16:30:57.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:57.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:57.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:57.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 11 16:30:57.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:57.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:57.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:57.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:57.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:57.805: INFO:
Nov 11 16:30:59.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:59.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:59.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:30:59.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 11 16:30:59.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:30:59.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:30:59.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:59.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:59.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:30:59.805: INFO:
Nov 11 16:31:01.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:01.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:01.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:01.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 11 16:31:01.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:01.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:01.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:01.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:01.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:01.805: INFO:
Nov 11 16:31:03.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:03.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:03.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:03.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 11 16:31:03.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:03.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:03.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:03.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:03.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:03.804: INFO:
Nov 11 16:31:05.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:05.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:05.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:05.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 11 16:31:05.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:05.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:05.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:05.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:05.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:05.808: INFO:
Nov 11 16:31:07.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:07.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:07.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:07.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 11 16:31:07.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:07.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:07.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:07.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:07.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:07.805: INFO:
Nov 11 16:31:09.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:09.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:09.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:09.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 11 16:31:09.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:09.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:09.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:09.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:09.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:09.806: INFO:
Nov 11 16:31:11.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:11.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:11.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:11.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 11 16:31:11.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:11.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:11.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:11.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:11.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:11.808: INFO:
Nov 11 16:31:13.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:13.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:13.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:13.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 11 16:31:13.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:13.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:13.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:13.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:13.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:13.807: INFO:
Nov 11 16:31:15.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:15.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:15.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:15.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 11 16:31:15.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:15.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:15.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:15.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:15.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:15.809: INFO:
Nov 11 16:31:17.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:17.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:17.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:17.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 11 16:31:17.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:17.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:17.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:17.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:17.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:17.804: INFO:
Nov 11 16:31:19.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:19.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:19.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:19.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 11 16:31:19.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:19.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:19.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:19.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:19.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:19.808: INFO:
Nov 11 16:31:21.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:21.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:21.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:21.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 11 16:31:21.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:21.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:21.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:21.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:21.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:21.807: INFO:
Nov 11 16:31:23.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:23.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:23.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:23.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 11 16:31:23.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:23.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:23.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:23.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:23.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:23.804: INFO:
Nov 11 16:31:25.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:25.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:25.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:25.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 11 16:31:25.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:25.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:25.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:25.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:25.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:25.807: INFO:
Nov 11 16:31:27.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:27.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:27.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:27.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 11 16:31:27.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:27.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:27.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:27.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:27.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:27.804: INFO:
Nov 11 16:31:29.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:29.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:29.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:29.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 11 16:31:29.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:29.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:29.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:29.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:29.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:29.807: INFO:
Nov 11 16:31:31.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:31.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:31.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:31.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 11 16:31:31.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:31.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:31.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:31.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:31.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:31.808: INFO:
Nov 11 16:31:33.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:33.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:33.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:33.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 11 16:31:33.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:33.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:33.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:33.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:33.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:33.807: INFO:
Nov 11 16:31:35.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:35.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:35.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:35.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 11 16:31:35.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:35.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:35.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:35.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:35.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:35.810: INFO:
Nov 11 16:31:37.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:37.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:37.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:37.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 11 16:31:37.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:37.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:37.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:37.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:37.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:37.804: INFO:
Nov 11 16:31:39.830: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:39.830: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:39.830: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:39.830: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 11 16:31:39.830: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:39.830: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:39.830: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:39.830: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:39.830: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:39.830: INFO:
Nov 11 16:31:41.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:41.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:41.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:41.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 11 16:31:41.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:41.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:41.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:41.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:41.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:41.806: INFO:
Nov 11 16:31:43.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:43.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:43.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:43.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 11 16:31:43.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:43.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:43.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:43.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:43.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:43.808: INFO:
Nov 11 16:31:45.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:45.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:45.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:45.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 11 16:31:45.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:45.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:45.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:45.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:45.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:45.816: INFO:
Nov 11 16:31:47.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:47.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:47.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:47.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 11 16:31:47.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:47.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:47.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:47.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:47.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:47.806: INFO:
Nov 11 16:31:49.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:49.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:49.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:49.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 11 16:31:49.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:49.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:49.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:49.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:49.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:49.806: INFO:
Nov 11 16:31:51.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:51.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:51.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:51.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 11 16:31:51.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:51.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:51.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:51.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:51.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:51.804: INFO:
Nov 11 16:31:53.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:53.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:53.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:53.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 11 16:31:53.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:53.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:53.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:53.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:53.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:53.807: INFO:
Nov 11 16:31:55.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:55.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:55.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:55.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 11 16:31:55.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:55.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:55.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:55.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:55.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:55.808: INFO:
Nov 11 16:31:57.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:57.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:57.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:57.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 11 16:31:57.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:57.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:57.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:57.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:57.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:57.807: INFO:
Nov 11 16:31:59.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:59.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:59.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:31:59.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 11 16:31:59.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:31:59.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:31:59.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:59.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:59.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:31:59.808: INFO:
Nov 11 16:32:01.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:01.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:01.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:01.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 11 16:32:01.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:01.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:01.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:01.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:01.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:01.807: INFO:
Nov 11 16:32:03.995: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:03.995: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:03.995: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:03.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 11 16:32:03.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:03.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:03.995: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:03.995: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:03.995: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:03.995: INFO:
Nov 11 16:32:05.852: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:05.852: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:05.852: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:05.852: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 11 16:32:05.852: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:05.852: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:05.852: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:05.852: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:05.852: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:05.852: INFO:
Nov 11 16:32:07.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:07.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:07.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:07.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 11 16:32:07.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:07.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:07.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:07.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:07.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:07.805: INFO:
Nov 11 16:32:09.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:09.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:09.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:09.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 11 16:32:09.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:09.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:09.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:09.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:09.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:09.805: INFO:
Nov 11 16:32:11.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:11.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:11.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:11.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 11 16:32:11.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:11.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:11.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:11.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:11.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:11.807: INFO:
Nov 11 16:32:13.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:13.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:13.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:13.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 11 16:32:13.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:13.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:13.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:13.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:13.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:13.814: INFO:
Nov 11 16:32:15.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:15.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:15.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:15.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 11 16:32:15.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:15.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:15.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:15.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:15.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:15.810: INFO:
Nov 11 16:32:17.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:17.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:17.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:17.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 11 16:32:17.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:17.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:17.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:17.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:17.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:17.805: INFO:
Nov 11 16:32:19.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:19.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:19.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:19.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 11 16:32:19.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:19.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:19.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:19.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:19.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:19.816: INFO:
Nov 11 16:32:21.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:21.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:21.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:21.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 11 16:32:21.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:21.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:21.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:21.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:21.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:21.806: INFO:
Nov 11 16:32:23.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:23.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:23.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:23.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 11 16:32:23.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:23.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:23.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:23.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:23.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:23.809: INFO:
Nov 11 16:32:25.869: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:25.869: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:25.869: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:25.869: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 11 16:32:25.869: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:25.869: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:25.869: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:25.869: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:25.869: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:25.869: INFO:
Nov 11 16:32:27.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:27.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:27.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:27.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 11 16:32:27.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:27.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:27.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:27.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:27.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:27.808: INFO:
Nov 11 16:32:29.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:29.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:29.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:29.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 11 16:32:29.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:29.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:29.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:29.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:29.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:29.813: INFO:
Nov 11 16:32:31.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:31.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:31.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:31.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 11 16:32:31.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:31.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:31.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:31.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:31.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:31.808: INFO:
Nov 11 16:32:33.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:33.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:33.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:33.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 11 16:32:33.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:33.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:33.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:33.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:33.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:33.810: INFO:
Nov 11 16:32:35.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:35.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:35.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:35.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 11 16:32:35.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:35.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:35.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:35.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:35.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:35.813: INFO:
Nov 11 16:32:37.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:37.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:37.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:37.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 11 16:32:37.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:37.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:37.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:37.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:37.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:37.818: INFO:
Nov 11 16:32:39.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:39.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:39.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:39.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 11 16:32:39.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:39.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:39.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:39.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:39.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:39.807: INFO:
Nov 11 16:32:41.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:41.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:41.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:41.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 11 16:32:41.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:41.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:41.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:41.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:41.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:41.807: INFO:
Nov 11 16:32:43.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:43.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:43.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:43.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 11 16:32:43.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:43.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:43.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:43.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:43.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:43.806: INFO:
Nov 11 16:32:45.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:45.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:45.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:45.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 11 16:32:45.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:45.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:45.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:45.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:45.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:45.820: INFO:
Nov 11 16:32:47.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:47.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:47.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:47.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 11 16:32:47.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:47.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:47.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:47.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:47.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:47.807: INFO:
Nov 11 16:32:49.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:49.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:49.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:49.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 11 16:32:49.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:49.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:49.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:49.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:49.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:49.806: INFO:
Nov 11 16:32:51.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:51.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:51.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:51.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 11 16:32:51.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:51.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:51.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:51.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:51.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:51.807: INFO:
Nov 11 16:32:53.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:53.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:53.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:53.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 11 16:32:53.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:53.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:53.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:53.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:53.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:53.806: INFO:
Nov 11 16:32:55.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:55.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:55.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:55.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 11 16:32:55.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:55.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:55.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:55.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:55.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:55.809: INFO:
Nov 11 16:32:57.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:57.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:57.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:57.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 11 16:32:57.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:57.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:57.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:57.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:57.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:57.807: INFO:
Nov 11 16:32:59.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:59.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:59.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:32:59.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 11 16:32:59.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:32:59.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:32:59.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:59.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:59.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:32:59.808: INFO:
Nov 11 16:33:01.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:01.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:01.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:01.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 11 16:33:01.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:01.805: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:01.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:01.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:01.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:01.805: INFO:
Nov 11 16:33:03.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:03.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:03.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:03.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 11 16:33:03.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:03.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:03.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:03.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:03.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:03.811: INFO:
Nov 11 16:33:05.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:05.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:05.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:05.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 11 16:33:05.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:05.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:05.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:05.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:05.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:05.816: INFO:
Nov 11 16:33:07.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:07.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:07.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:07.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 11 16:33:07.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:07.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:07.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:07.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:07.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:07.812: INFO:
Nov 11 16:33:09.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:09.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:09.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:09.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 11 16:33:09.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:09.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:09.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:09.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:09.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:09.807: INFO:
Nov 11 16:33:11.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:11.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:11.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:11.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 11 16:33:11.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:11.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:11.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:11.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:11.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:11.807: INFO:
Nov 11 16:33:13.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:13.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:13.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:13.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 11 16:33:13.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:13.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:13.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:13.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:13.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:13.809: INFO:
Nov 11 16:33:15.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:15.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:15.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:15.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 11 16:33:15.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:15.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:15.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:15.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:15.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:15.814: INFO:
Nov 11 16:33:17.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:17.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:17.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:17.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 11 16:33:17.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:17.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:17.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:17.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:17.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:17.807: INFO:
Nov 11 16:33:19.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:19.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:19.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:19.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 11 16:33:19.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:19.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:19.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:19.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:19.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:19.810: INFO:
Nov 11 16:33:21.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:21.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:21.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:21.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 11 16:33:21.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:21.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:21.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:21.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:21.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:21.809: INFO:
Nov 11 16:33:23.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:23.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:23.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:23.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 11 16:33:23.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:23.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:23.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:23.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:23.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:23.813: INFO:
Nov 11 16:33:25.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:25.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:25.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:25.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 11 16:33:25.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:25.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:25.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:25.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:25.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:25.818: INFO:
Nov 11 16:33:27.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:27.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:27.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:27.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 11 16:33:27.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:27.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:27.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:27.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:27.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:27.811: INFO:
Nov 11 16:33:29.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:29.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:29.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:29.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 11 16:33:29.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:29.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:29.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:29.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:29.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:29.809: INFO:
Nov 11 16:33:31.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:31.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:31.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:31.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 11 16:33:31.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:31.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:31.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:31.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:31.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:31.807: INFO:
Nov 11 16:33:33.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:33.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:33.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:33.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 11 16:33:33.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:33.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:33.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:33.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:33.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:33.811: INFO:
Nov 11 16:33:35.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:35.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:35.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:35.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 11 16:33:35.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:35.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:35.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:35.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:35.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:35.810: INFO:
Nov 11 16:33:37.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:37.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:37.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:37.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 11 16:33:37.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:37.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:37.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:37.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:37.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:37.811: INFO:
Nov 11 16:33:39.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:39.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:39.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:39.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 11 16:33:39.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:39.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:39.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:39.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:39.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:39.820: INFO:
Nov 11 16:33:41.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:41.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:41.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:41.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 11 16:33:41.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:41.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:41.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:41.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:41.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:41.809: INFO:
Nov 11 16:33:43.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:43.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:43.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:43.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 11 16:33:43.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:43.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:43.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:43.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:43.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:43.809: INFO:
Nov 11 16:33:45.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:45.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:45.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:45.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 11 16:33:45.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:45.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:45.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:45.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:45.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:45.810: INFO:
Nov 11 16:33:47.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:47.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:47.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:47.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 11 16:33:47.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:47.822: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:47.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:47.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:47.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:47.822: INFO:
Nov 11 16:33:49.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:49.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:49.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:49.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 11 16:33:49.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:49.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:49.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:49.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:49.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:49.813: INFO:
Nov 11 16:33:51.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:51.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:51.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:51.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 11 16:33:51.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:51.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:51.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:51.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:51.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:51.812: INFO:
Nov 11 16:33:53.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:53.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:53.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:53.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 11 16:33:53.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:53.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:53.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:53.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:53.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:53.809: INFO:
Nov 11 16:33:55.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:55.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:55.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:55.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 11 16:33:55.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:55.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:55.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:55.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:55.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:55.809: INFO:
Nov 11 16:33:57.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:57.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:57.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:57.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 11 16:33:57.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:57.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:57.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:57.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:57.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:57.808: INFO:
Nov 11 16:33:59.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:59.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:59.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:33:59.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 11 16:33:59.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:33:59.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:33:59.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:59.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:59.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:33:59.815: INFO:
Nov 11 16:34:01.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:01.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:01.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:01.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 11 16:34:01.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:01.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:01.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:01.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:01.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:01.808: INFO:
Nov 11 16:34:03.997: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:03.997: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:03.997: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:03.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 11 16:34:03.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:03.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:03.997: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:03.997: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:03.997: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:03.997: INFO:
Nov 11 16:34:05.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:05.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:05.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:05.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 11 16:34:05.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:05.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:05.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:05.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:05.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:05.815: INFO:
Nov 11 16:34:07.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:07.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:07.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:07.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 11 16:34:07.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:07.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:07.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:07.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:07.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:07.806: INFO:
Nov 11 16:34:09.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:09.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:09.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:09.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 11 16:34:09.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:09.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:09.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:09.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:09.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:09.811: INFO:
Nov 11 16:34:11.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:11.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:11.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:11.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 11 16:34:11.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:11.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:11.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:11.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:11.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:11.809: INFO:
Nov 11 16:34:13.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:13.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:13.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:13.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 11 16:34:13.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:13.806: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:13.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:13.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:13.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:13.806: INFO:
Nov 11 16:34:15.852: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:15.852: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:15.853: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:15.853: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 11 16:34:15.853: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:15.853: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:15.853: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:15.853: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:15.853: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:15.853: INFO:
Nov 11 16:34:17.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:17.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:17.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:17.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 11 16:34:17.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:17.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:17.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:17.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:17.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:17.808: INFO:
Nov 11 16:34:19.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:19.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:19.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:19.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 11 16:34:19.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:19.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:19.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:19.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:19.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:19.816: INFO:
Nov 11 16:34:21.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:21.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:21.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:21.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 11 16:34:21.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:21.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:21.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:21.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:21.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:21.811: INFO:
Nov 11 16:34:23.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:23.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:23.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:23.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 11 16:34:23.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:23.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:23.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:23.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:23.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:23.807: INFO:
Nov 11 16:34:25.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:25.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:25.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:25.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 11 16:34:25.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:25.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:25.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:25.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:25.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:25.816: INFO:
Nov 11 16:34:27.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:27.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:27.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:27.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 11 16:34:27.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:27.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:27.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:27.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:27.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:27.808: INFO:
Nov 11 16:34:29.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:29.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:29.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:29.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 11 16:34:29.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:29.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:29.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:29.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:29.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:29.807: INFO:
Nov 11 16:34:31.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:31.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:31.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:31.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 11 16:34:31.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:31.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:31.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:31.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:31.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:31.807: INFO:
Nov 11 16:34:33.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:33.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:33.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:33.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 11 16:34:33.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:33.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:33.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:33.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:33.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:33.804: INFO:
Nov 11 16:34:35.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:35.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:35.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:35.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 11 16:34:35.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:35.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:35.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:35.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:35.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:35.811: INFO:
Nov 11 16:34:37.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:37.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:37.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:37.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 11 16:34:37.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:37.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:37.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:37.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:37.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:37.810: INFO:
Nov 11 16:34:39.830: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:39.830: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:39.830: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:39.830: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 11 16:34:39.830: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:39.830: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:39.830: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:39.830: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:39.830: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:39.830: INFO:
Nov 11 16:34:41.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:41.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:41.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:41.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 11 16:34:41.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:41.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:41.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:41.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:41.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:41.810: INFO:
Nov 11 16:34:43.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:43.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:43.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:43.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 11 16:34:43.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:43.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:43.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:43.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:43.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:43.813: INFO:
Nov 11 16:34:45.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:45.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:45.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:45.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 11 16:34:45.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:45.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:45.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:45.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:45.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:45.810: INFO:
Nov 11 16:34:47.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:47.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:47.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:47.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 11 16:34:47.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:47.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:47.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:47.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:47.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:47.813: INFO:
Nov 11 16:34:49.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:49.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:49.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:49.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 11 16:34:49.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:49.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:49.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:49.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:49.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:49.814: INFO:
Nov 11 16:34:51.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:51.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:51.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:51.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 11 16:34:51.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:51.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:51.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:51.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:51.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:51.817: INFO:
Nov 11 16:34:53.999: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:53.999: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:53.999: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:53.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 11 16:34:53.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:53.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:53.999: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:53.999: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:53.999: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:53.999: INFO:
Nov 11 16:34:55.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:55.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:55.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:55.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 11 16:34:55.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:55.822: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:55.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:55.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:55.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:55.822: INFO:
Nov 11 16:34:57.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:57.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:57.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:57.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 11 16:34:57.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:57.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:57.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:57.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:57.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:57.812: INFO:
Nov 11 16:34:59.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:59.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:59.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:34:59.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 11 16:34:59.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:34:59.819: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:34:59.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:59.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:59.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:34:59.819: INFO:
Nov 11 16:35:01.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:01.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:01.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:01.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 11 16:35:01.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:01.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:01.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:01.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:01.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:01.812: INFO:
Nov 11 16:35:03.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:03.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:03.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:03.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 11 16:35:03.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:03.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:03.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:03.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:03.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:03.812: INFO:
Nov 11 16:35:05.826: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:05.826: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:05.826: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:05.826: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 11 16:35:05.826: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:05.826: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:05.826: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:05.826: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:05.826: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:05.826: INFO:
Nov 11 16:35:07.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:07.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:07.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:07.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 11 16:35:07.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:07.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:07.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:07.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:07.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:07.813: INFO:
Nov 11 16:35:09.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:09.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:09.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:09.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 11 16:35:09.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:09.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:09.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:09.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:09.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:09.813: INFO:
Nov 11 16:35:11.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:11.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:11.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:11.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 11 16:35:11.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:11.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:11.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:11.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:11.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:11.811: INFO:
Nov 11 16:35:13.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:13.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:13.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:13.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 11 16:35:13.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:13.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:13.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:13.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:13.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:13.815: INFO:
Nov 11 16:35:15.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:15.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:15.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:15.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 11 16:35:15.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:15.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:15.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:15.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:15.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:15.820: INFO:
Nov 11 16:35:17.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:17.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:17.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:17.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 11 16:35:17.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:17.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:17.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:17.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:17.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:17.809: INFO:
Nov 11 16:35:19.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:19.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:19.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:19.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 11 16:35:19.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:19.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:19.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:19.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:19.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:19.812: INFO:
Nov 11 16:35:21.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:21.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:21.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:21.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 11 16:35:21.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:21.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:21.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:21.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:21.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:21.817: INFO:
Nov 11 16:35:23.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:23.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:23.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:23.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 11 16:35:23.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:23.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:23.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:23.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:23.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:23.810: INFO:
Nov 11 16:35:25.831: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:25.831: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:25.831: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:25.831: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 11 16:35:25.831: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:25.831: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:25.831: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:25.831: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:25.831: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:25.831: INFO:
Nov 11 16:35:27.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:27.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:27.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:27.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 11 16:35:27.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:27.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:27.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:27.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:27.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:27.815: INFO:
Nov 11 16:35:29.824: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:29.824: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:29.824: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:29.824: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 11 16:35:29.824: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:29.824: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:29.824: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:29.824: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:29.824: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:29.824: INFO:
Nov 11 16:35:31.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:31.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:31.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:31.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 11 16:35:31.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:31.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:31.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:31.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:31.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:31.816: INFO:
Nov 11 16:35:33.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:33.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:33.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:33.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 11 16:35:33.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:33.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:33.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:33.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:33.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:33.820: INFO:
Nov 11 16:35:35.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:35.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:35.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:35.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 11 16:35:35.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:35.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:35.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:35.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:35.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:35.813: INFO:
Nov 11 16:35:37.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:37.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:37.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:37.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 11 16:35:37.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:37.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:37.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:37.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:37.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:37.820: INFO:
Nov 11 16:35:39.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:39.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:39.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:39.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 11 16:35:39.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:39.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:39.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:39.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:39.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:39.812: INFO:
Nov 11 16:35:41.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:41.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:41.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:41.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 11 16:35:41.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:41.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:41.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:41.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:41.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:41.817: INFO:
Nov 11 16:35:44.003: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:44.003: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:44.003: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:44.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 11 16:35:44.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:44.003: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:44.003: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:44.003: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:44.003: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:44.003: INFO:
Nov 11 16:35:45.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:45.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:45.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:45.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 11 16:35:45.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:45.823: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:45.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:45.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:45.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:45.823: INFO:
Nov 11 16:35:47.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:47.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:47.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:47.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 11 16:35:47.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:47.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:47.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:47.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:47.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:47.814: INFO:
Nov 11 16:35:49.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:49.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:49.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:49.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 11 16:35:49.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:49.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:49.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:49.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:49.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:49.815: INFO:
Nov 11 16:35:51.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:51.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:51.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:51.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 11 16:35:51.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:51.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:51.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:51.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:51.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:51.818: INFO:
Nov 11 16:35:53.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:53.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:53.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:53.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 11 16:35:53.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:53.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:53.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:53.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:53.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:53.813: INFO:
Nov 11 16:35:55.826: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:55.826: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:55.826: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:55.826: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 11 16:35:55.826: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:55.826: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:55.826: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:55.826: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:55.826: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:55.826: INFO:
Nov 11 16:35:57.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:57.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:57.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:57.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 11 16:35:57.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:57.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:57.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:57.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:57.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:57.820: INFO:
Nov 11 16:35:59.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:59.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:59.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:35:59.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 11 16:35:59.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:35:59.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:35:59.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:59.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:59.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:35:59.815: INFO:
Nov 11 16:36:01.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:01.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:01.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:01.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 11 16:36:01.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:01.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:01.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:01.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:01.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:01.811: INFO:
Nov 11 16:36:03.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:03.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:03.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:03.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 11 16:36:03.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:03.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:03.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:03.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:03.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:03.814: INFO:
Nov 11 16:36:05.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:05.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:05.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:05.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 11 16:36:05.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:05.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:05.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:05.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:05.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:05.820: INFO:
Nov 11 16:36:07.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:07.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:07.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:07.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 11 16:36:07.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:07.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:07.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:07.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:07.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:07.813: INFO:
Nov 11 16:36:09.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:09.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:09.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:09.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 11 16:36:09.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:09.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:09.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:09.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:09.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:09.816: INFO:
Nov 11 16:36:11.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:11.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:11.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:11.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 11 16:36:11.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:11.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:11.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:11.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:11.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:11.817: INFO:
Nov 11 16:36:13.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:13.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:13.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:13.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 11 16:36:13.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:13.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:13.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:13.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:13.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:13.817: INFO:
Nov 11 16:36:15.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:15.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:15.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:15.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 11 16:36:15.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:15.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:15.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:15.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:15.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:15.812: INFO:
Nov 11 16:36:17.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:17.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:17.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:17.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 11 16:36:17.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:17.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:17.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:17.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:17.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:17.817: INFO:
Nov 11 16:36:19.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:19.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:19.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:19.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 11 16:36:19.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:19.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:19.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:19.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:19.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:19.808: INFO:
Nov 11 16:36:21.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:21.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:21.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:21.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 11 16:36:21.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:21.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:21.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:21.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:21.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:21.809: INFO:
Nov 11 16:36:23.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:23.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:23.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:23.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 11 16:36:23.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:23.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:23.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:23.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:23.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:23.810: INFO:
Nov 11 16:36:25.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:25.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:25.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:25.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 11 16:36:25.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:25.825: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:25.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:25.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:25.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:25.825: INFO:
Nov 11 16:36:27.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:27.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:27.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:27.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 11 16:36:27.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:27.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:27.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:27.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:27.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:27.812: INFO:
Nov 11 16:36:29.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:29.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:29.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:29.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 11 16:36:29.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:29.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:29.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:29.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:29.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:29.815: INFO:
Nov 11 16:36:31.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:31.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:31.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:31.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 11 16:36:31.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:31.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:31.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:31.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:31.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:31.809: INFO:
Nov 11 16:36:33.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:33.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:33.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:33.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 11 16:36:33.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:33.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:33.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:33.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:33.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:33.813: INFO:
Nov 11 16:36:36.017: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:36.017: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:36.017: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:36.017: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (361 seconds elapsed)
Nov 11 16:36:36.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:36.017: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:36.017: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:36.017: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:36.017: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:36.017: INFO:
Nov 11 16:36:37.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:37.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:37.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:37.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 11 16:36:37.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:37.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:37.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:37.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:37.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:37.812: INFO:
Nov 11 16:36:39.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:39.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:39.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:39.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 11 16:36:39.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:39.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:39.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:39.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:39.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:39.813: INFO:
Nov 11 16:36:41.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:41.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:41.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:41.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 11 16:36:41.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:41.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:41.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:41.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:41.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:41.812: INFO:
Nov 11 16:36:43.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:43.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:43.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:43.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 11 16:36:43.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:43.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:43.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:43.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:43.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:43.810: INFO:
Nov 11 16:36:45.838: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:45.838: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:45.838: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:45.838: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 11 16:36:45.838: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:45.838: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:45.838: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:45.838: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:45.838: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:45.838: INFO:
Nov 11 16:36:47.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:47.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:47.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:47.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 11 16:36:47.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:47.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:47.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:47.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:47.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:47.811: INFO:
Nov 11 16:36:49.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:49.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:49.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:49.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 11 16:36:49.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:49.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:49.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:49.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:49.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:49.814: INFO:
Nov 11 16:36:51.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:51.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:51.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:51.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 11 16:36:51.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:51.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:51.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:51.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:51.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:51.812: INFO:
Nov 11 16:36:53.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:53.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:53.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:53.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 11 16:36:53.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:53.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:53.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:53.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:53.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:53.815: INFO:
Nov 11 16:36:55.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:55.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:55.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:55.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 11 16:36:55.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:55.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:55.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:55.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:55.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:55.820: INFO:
Nov 11 16:36:57.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:57.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:57.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:36:57.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 11 16:36:57.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:36:57.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:36:57.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:57.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:57.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:36:57.809: INFO:
Nov 11 16:37:00.003: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:00.003: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:00.003: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:00.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 11 16:37:00.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:00.003: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:00.003: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:00.003: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:00.003: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:00.003: INFO:
Nov 11 16:37:01.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:01.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:01.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:01.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 11 16:37:01.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:01.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:01.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:01.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:01.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:01.814: INFO:
Nov 11 16:37:03.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:03.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:03.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:03.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 11 16:37:03.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:03.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:03.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:03.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:03.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:03.809: INFO:
Nov 11 16:37:05.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:05.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:05.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:05.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 11 16:37:05.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:05.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:05.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:05.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:05.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:05.810: INFO:
Nov 11 16:37:07.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:07.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:07.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:07.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 11 16:37:07.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:07.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:07.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:07.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:07.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:07.811: INFO:
Nov 11 16:37:09.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:09.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:09.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:09.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 11 16:37:09.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:09.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:09.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:09.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:09.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:09.810: INFO:
Nov 11 16:37:11.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:11.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:11.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:11.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 11 16:37:11.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:11.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:11.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:11.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:11.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:11.811: INFO:
Nov 11 16:37:13.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:13.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:13.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:13.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 11 16:37:13.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:13.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:13.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:13.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:13.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:13.820: INFO:
Nov 11 16:37:15.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:15.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:15.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:15.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 11 16:37:15.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:15.822: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:15.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:15.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:15.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:15.822: INFO:
Nov 11 16:37:17.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:17.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:17.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:17.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 11 16:37:17.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:17.807: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:17.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:17.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:17.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:17.807: INFO:
Nov 11 16:37:19.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:19.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:19.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:19.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 11 16:37:19.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:19.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:19.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:19.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:19.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:19.817: INFO:
Nov 11 16:37:21.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:21.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:21.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:21.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 11 16:37:21.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:21.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:21.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:21.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:21.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:21.814: INFO:
Nov 11 16:37:23.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:23.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:23.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:23.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 11 16:37:23.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:23.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:23.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:23.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:23.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:23.810: INFO:
Nov 11 16:37:25.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:25.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:25.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:25.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 11 16:37:25.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:25.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:25.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:25.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:25.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:25.815: INFO:
Nov 11 16:37:27.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:27.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:27.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:27.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 11 16:37:27.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:27.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:27.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:27.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:27.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:27.809: INFO:
Nov 11 16:37:29.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:29.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:29.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:29.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 11 16:37:29.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:29.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:29.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:29.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:29.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:29.812: INFO:
Nov 11 16:37:31.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:31.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:31.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:31.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 11 16:37:31.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:31.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:31.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:31.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:31.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:31.811: INFO:
Nov 11 16:37:33.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:33.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:33.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:33.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 11 16:37:33.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:33.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:33.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:33.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:33.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:33.814: INFO:
Nov 11 16:37:35.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:35.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:35.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:35.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 11 16:37:35.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:35.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:35.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:35.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:35.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:35.818: INFO:
Nov 11 16:37:37.829: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:37.829: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:37.829: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:37.829: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 11 16:37:37.829: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:37.829: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:37.829: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:37.829: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:37.829: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:37.829: INFO:
Nov 11 16:37:39.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:39.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:39.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:39.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 11 16:37:39.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:39.819: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:39.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:39.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:39.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:39.819: INFO:
Nov 11 16:37:41.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:41.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:41.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:41.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 11 16:37:41.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:41.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:41.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:41.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:41.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:41.815: INFO:
Nov 11 16:37:43.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:43.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:43.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:43.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 11 16:37:43.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:43.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:43.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:43.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:43.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:43.815: INFO:
Nov 11 16:37:45.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:45.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:45.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:45.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 11 16:37:45.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:45.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:45.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:45.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:45.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:45.815: INFO:
Nov 11 16:37:47.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:47.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:47.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:47.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 11 16:37:47.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:47.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:47.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:47.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:47.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:47.817: INFO:
Nov 11 16:37:49.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:49.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:49.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:49.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 11 16:37:49.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:49.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:49.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:49.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:49.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:49.815: INFO:
Nov 11 16:37:51.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:51.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:51.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:51.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 11 16:37:51.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:51.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:51.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:51.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:51.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:51.817: INFO:
Nov 11 16:37:53.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:53.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:53.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:53.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 11 16:37:53.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:53.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:53.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:53.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:53.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:53.813: INFO:
Nov 11 16:37:55.828: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:55.828: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:55.828: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:55.828: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 11 16:37:55.828: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:55.828: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:55.828: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:55.828: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:55.828: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:55.828: INFO:
Nov 11 16:37:57.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:57.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:57.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:57.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 11 16:37:57.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:57.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:57.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:57.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:57.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:57.814: INFO:
Nov 11 16:37:59.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:59.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:59.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:37:59.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 11 16:37:59.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:37:59.822: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:37:59.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:59.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:59.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:37:59.822: INFO:
Nov 11 16:38:01.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:01.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:01.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:01.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 11 16:38:01.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:01.822: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:01.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:01.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:01.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:01.822: INFO:
Nov 11 16:38:03.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:03.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:03.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:03.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 11 16:38:03.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:03.825: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:03.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:03.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:03.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:03.825: INFO:
Nov 11 16:38:05.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:05.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:05.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:05.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 11 16:38:05.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:05.823: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:05.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:05.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:05.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:05.823: INFO:
Nov 11 16:38:07.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:07.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:07.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:07.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 11 16:38:07.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:07.819: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:07.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:07.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:07.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:07.819: INFO:
Nov 11 16:38:10.008: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:10.008: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:10.008: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:10.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 11 16:38:10.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:10.008: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:10.008: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:10.008: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:10.008: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:10.008: INFO:
Nov 11 16:38:11.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:11.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:11.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:11.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 11 16:38:11.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:11.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:11.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:11.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:11.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:11.818: INFO:
Nov 11 16:38:13.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:13.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:13.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:13.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 11 16:38:13.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:13.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:13.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:13.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:13.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:13.817: INFO:
Nov 11 16:38:15.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:15.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:15.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:15.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 11 16:38:15.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:15.823: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:15.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:15.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:15.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:15.823: INFO:
Nov 11 16:38:17.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:17.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:17.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:17.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 11 16:38:17.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:17.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:17.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:17.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:17.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:17.813: INFO:
Nov 11 16:38:19.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:19.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:19.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:19.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 11 16:38:19.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:19.825: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:19.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:19.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:19.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:19.825: INFO:
Nov 11 16:38:21.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:21.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:21.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:21.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 11 16:38:21.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:21.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:21.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:21.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:21.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:21.820: INFO:
Nov 11 16:38:23.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:23.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:23.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:23.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 11 16:38:23.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:23.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:23.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:23.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:23.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:23.816: INFO:
Nov 11 16:38:25.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:25.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:25.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:25.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 11 16:38:25.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:25.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:25.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:25.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:25.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:25.811: INFO:
Nov 11 16:38:27.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:27.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:27.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:27.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 11 16:38:27.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:27.825: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:27.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:27.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:27.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:27.825: INFO:
Nov 11 16:38:29.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:29.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:29.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:29.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 11 16:38:29.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:29.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:29.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:29.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:29.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:29.812: INFO:
Nov 11 16:38:31.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:31.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:31.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:31.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 11 16:38:31.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:31.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:31.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:31.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:31.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:31.815: INFO:
Nov 11 16:38:33.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:33.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:33.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:33.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 11 16:38:33.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:33.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:33.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:33.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:33.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:33.810: INFO:
Nov 11 16:38:35.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:35.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:35.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:35.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 11 16:38:35.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:35.822: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:35.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:35.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:35.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:35.822: INFO:
Nov 11 16:38:37.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:37.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:37.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:37.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 11 16:38:37.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:37.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:37.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:37.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:37.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:37.813: INFO:
Nov 11 16:38:39.821: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:39.821: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:39.821: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:39.821: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 11 16:38:39.821: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:39.821: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:39.821: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:39.821: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:39.821: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:39.821: INFO:
Nov 11 16:38:42.001: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:42.001: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:42.001: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:42.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 11 16:38:42.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:42.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:42.002: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:42.002: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:42.002: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:42.002: INFO:
Nov 11 16:38:43.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:43.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:43.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:43.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 11 16:38:43.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:43.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:43.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:43.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:43.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:43.814: INFO:
Nov 11 16:38:45.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:45.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:45.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:45.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 11 16:38:45.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:45.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:45.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:45.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:45.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:45.817: INFO:
Nov 11 16:38:47.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:47.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:47.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:47.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 11 16:38:47.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:47.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:47.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:47.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:47.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:47.816: INFO:
Nov 11 16:38:49.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:49.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:49.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:49.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 11 16:38:49.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:49.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:49.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:49.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:49.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:49.817: INFO:
Nov 11 16:38:51.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:51.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:51.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:51.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 11 16:38:51.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:51.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:51.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:51.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:51.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:51.815: INFO:
Nov 11 16:38:53.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:53.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:53.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:53.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 11 16:38:53.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:53.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:53.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:53.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:53.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:53.813: INFO:
Nov 11 16:38:55.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:55.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:55.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:55.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 11 16:38:55.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:55.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:55.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:55.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:55.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:55.810: INFO:
Nov 11 16:38:57.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:57.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:57.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:57.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 11 16:38:57.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:57.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:57.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:57.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:57.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:57.816: INFO:
Nov 11 16:38:59.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:59.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:59.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:38:59.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 11 16:38:59.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:38:59.819: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:38:59.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:59.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:59.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:38:59.819: INFO:
Nov 11 16:39:01.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:01.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:01.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:01.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 11 16:39:01.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:01.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:01.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:01.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:01.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:01.810: INFO:
Nov 11 16:39:03.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:03.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:03.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:03.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 11 16:39:03.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:03.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:03.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:03.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:03.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:03.813: INFO:
Nov 11 16:39:05.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:05.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:05.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:05.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 11 16:39:05.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:05.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:05.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:05.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:05.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:05.814: INFO:
Nov 11 16:39:07.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:07.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:07.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:07.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 11 16:39:07.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:07.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:07.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:07.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:07.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:07.809: INFO:
Nov 11 16:39:09.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:09.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:09.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:09.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 11 16:39:09.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:09.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:09.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:09.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:09.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:09.809: INFO:
Nov 11 16:39:11.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:11.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:11.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:11.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 11 16:39:11.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:11.817: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:11.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:11.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:11.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:11.817: INFO:
Nov 11 16:39:13.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:13.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:13.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:13.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 11 16:39:13.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:13.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:13.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:13.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:13.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:13.811: INFO:
Nov 11 16:39:15.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:15.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:15.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:15.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 11 16:39:15.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:15.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:15.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:15.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:15.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:15.813: INFO:
Nov 11 16:39:17.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:17.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:17.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:17.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 11 16:39:17.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:17.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:17.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:17.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:17.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:17.813: INFO:
Nov 11 16:39:19.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:19.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:19.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:19.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 11 16:39:19.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:19.823: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:19.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:19.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:19.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:19.823: INFO:
Nov 11 16:39:21.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:21.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:21.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:21.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 11 16:39:21.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:21.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:21.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:21.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:21.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:21.812: INFO:
Nov 11 16:39:23.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:23.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:23.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:23.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 11 16:39:23.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:23.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:23.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:23.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:23.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:23.808: INFO:
Nov 11 16:39:25.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:25.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:25.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:25.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 11 16:39:25.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:25.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:25.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:25.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:25.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:25.812: INFO:
Nov 11 16:39:27.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:27.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:27.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:27.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 11 16:39:27.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:27.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:27.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:27.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:27.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:27.811: INFO:
Nov 11 16:39:29.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:29.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:29.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:29.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 11 16:39:29.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:29.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:29.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:29.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:29.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:29.809: INFO:
Nov 11 16:39:31.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:31.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:31.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:31.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 11 16:39:31.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:31.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:31.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:31.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:31.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:31.812: INFO:
Nov 11 16:39:33.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:33.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:33.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:33.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 11 16:39:33.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:33.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:33.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:33.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:33.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:33.811: INFO:
Nov 11 16:39:35.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:35.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:35.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:35.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 11 16:39:35.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:35.820: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:35.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:35.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:35.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:35.820: INFO:
Nov 11 16:39:37.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:37.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:37.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:37.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 11 16:39:37.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:37.823: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:37.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:37.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:37.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:37.823: INFO:
Nov 11 16:39:40.001: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:40.001: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:40.001: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:40.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 11 16:39:40.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:40.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:40.001: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:40.001: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:40.001: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:40.001: INFO:
Nov 11 16:39:41.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:41.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:41.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:41.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 11 16:39:41.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:41.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:41.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:41.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:41.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:41.811: INFO:
Nov 11 16:39:43.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:43.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:43.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:43.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 11 16:39:43.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:43.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:43.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:43.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:43.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:43.811: INFO:
Nov 11 16:39:45.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:45.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:45.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:45.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 11 16:39:45.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:45.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:45.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:45.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:45.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:45.814: INFO:
Nov 11 16:39:47.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:47.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:47.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:47.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 11 16:39:47.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:47.809: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:47.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:47.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:47.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:47.809: INFO:
Nov 11 16:39:49.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:49.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:49.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:49.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 11 16:39:49.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:49.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:49.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:49.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:49.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:49.812: INFO:
Nov 11 16:39:51.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:51.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:51.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:51.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 11 16:39:51.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:51.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:51.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:51.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:51.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:51.810: INFO:
Nov 11 16:39:53.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:53.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:53.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:53.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 11 16:39:53.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:53.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:53.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:53.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:53.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:53.814: INFO:
Nov 11 16:39:55.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:55.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:55.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:55.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 11 16:39:55.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:55.819: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:55.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:55.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:55.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:55.819: INFO:
Nov 11 16:39:57.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:57.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:57.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:57.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 11 16:39:57.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:57.810: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:57.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:57.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:57.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:57.810: INFO:
Nov 11 16:39:59.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:59.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:59.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:39:59.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 11 16:39:59.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:39:59.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:39:59.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:59.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:59.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:39:59.816: INFO:
Nov 11 16:40:01.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:01.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:01.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:01.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 11 16:40:01.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:01.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:01.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:01.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:01.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:01.811: INFO:
Nov 11 16:40:03.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:03.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:03.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:03.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 11 16:40:03.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:03.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:03.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:03.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:03.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:03.811: INFO:
Nov 11 16:40:05.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:05.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:05.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:05.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 11 16:40:05.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:05.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:05.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:05.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:05.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:05.818: INFO:
Nov 11 16:40:07.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:07.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:07.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:07.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 11 16:40:07.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:07.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:07.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:07.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:07.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:07.812: INFO:
Nov 11 16:40:09.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:09.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:09.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:09.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 11 16:40:09.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:09.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:09.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:09.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:09.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:09.811: INFO:
Nov 11 16:40:11.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:11.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:11.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:11.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 11 16:40:11.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:11.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:11.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:11.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:11.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:11.814: INFO:
Nov 11 16:40:13.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:13.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:13.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:13.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 11 16:40:13.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:13.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:13.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:13.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:13.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:13.811: INFO:
Nov 11 16:40:15.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:15.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:15.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:15.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 11 16:40:15.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:15.818: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:15.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:15.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:15.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:15.818: INFO:
Nov 11 16:40:17.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:17.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:17.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:17.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 11 16:40:17.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:17.813: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:17.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:17.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:17.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:17.813: INFO:
Nov 11 16:40:19.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:19.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:19.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:19.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 11 16:40:19.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:19.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:19.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:19.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:19.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:19.811: INFO:
Nov 11 16:40:21.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:21.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:21.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:21.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 11 16:40:21.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:21.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:21.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:21.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:21.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:21.815: INFO:
Nov 11 16:40:23.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:23.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:23.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:23.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 11 16:40:23.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:23.808: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:23.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:23.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:23.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:23.808: INFO:
Nov 11 16:40:25.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:25.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:25.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:25.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 11 16:40:25.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:25.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:25.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:25.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:25.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:25.815: INFO:
Nov 11 16:40:27.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:27.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:27.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:27.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 11 16:40:27.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:27.814: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:27.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:27.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:27.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:27.814: INFO:
Nov 11 16:40:29.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:29.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:29.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:29.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 11 16:40:29.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:29.811: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:29.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:29.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:29.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:29.811: INFO:
Nov 11 16:40:31.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:31.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:31.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:31.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 11 16:40:31.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:31.816: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:31.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:31.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:31.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:31.816: INFO:
Nov 11 16:40:33.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:33.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:33.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:33.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 11 16:40:33.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:33.812: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:33.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:33.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:33.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:33.812: INFO:
Nov 11 16:40:35.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:35.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:35.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:35.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 11 16:40:35.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:35.815: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:35.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:35.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:35.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:35.815: INFO:
Nov 11 16:40:36.222: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:36.222: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:36.222: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 16:40:36.222: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (601 seconds elapsed)
Nov 11 16:40:36.222: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 16:40:36.222: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:36.222: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:36.222: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:36.222: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:36.222: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/11/22 16:40:36.223�[0m
�[1mSTEP:�[0m Found 127 events. �[38;5;243m11/11/22 16:40:36.376�[0m
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:27 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-whcdvl-control-plane-2s6hv_ffe9f81f-a5ff-4bc6-90ab-86446ca4b8ac became leader
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:28 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-whcdvl-control-plane-2s6hv_79992e68-f460-4a04-b90d-375ebaa3ebae became leader
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-64475449fc to 2
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for coredns-64475449fc: {replicaset-controller } SuccessfulCreate: Created pod: coredns-64475449fc-wn4xw
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for coredns-64475449fc: {replicaset-controller } SuccessfulCreate: Created pod: coredns-64475449fc-d6gdj
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for coredns-64475449fc-d6gdj: {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 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for coredns-64475449fc-wn4xw: {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 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-jc2n5
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:45 +0000 UTC - event for kube-proxy-jc2n5: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-jc2n5 to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:47 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-jc2n5
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:49 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-x8c7k
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:49 +0000 UTC - event for kube-proxy-x8c7k: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-x8c7k to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:51 +0000 UTC - event for kube-proxy-x8c7k: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.51_013c1ef249fd5d"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:56 +0000 UTC - event for kube-proxy-x8c7k: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container kube-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:56 +0000 UTC - event for kube-proxy-x8c7k: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container kube-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:25:56 +0000 UTC - event for kube-proxy-x8c7k: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.51_013c1ef249fd5d" in 4.991508348s (4.991529352s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:12 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-954b56d74 to 1
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:12 +0000 UTC - event for metrics-server-954b56d74: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-954b56d74-6dtnh
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:12 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {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 11 16:40:36.376: INFO: At 2022-11-11 16:26:14 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-56c5ff4bf8 to 1
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:14 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-56c5ff4bf8-p52w5
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:14 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {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 11 16:40:36.376: INFO: At 2022-11-11 16:26:15 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-bf56r
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:15 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:15 +0000 UTC - event for calico-node-bf56r: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-bf56r to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:24 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container upgrade-ipam
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:24 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container upgrade-ipam
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:24 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 8.651684663s (8.651690563s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:28 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:28 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container install-cni
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:28 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container install-cni
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:30 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-56c5ff4bf8-p52w5 to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:30 +0000 UTC - event for coredns-64475449fc-d6gdj: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-64475449fc-d6gdj to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:30 +0000 UTC - event for coredns-64475449fc-wn4xw: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-64475449fc-wn4xw to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:30 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-954b56d74-6dtnh to capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:31 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {kubelet capz-conf-whcdvl-control-plane-2s6hv} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b14fd9ce0bbb11b7d653e259d25be762c747155c649cbbe42fe6e5ddff789254": 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 11 16:40:36.376: INFO: At 2022-11-11 16:26:31 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:31 +0000 UTC - event for coredns-64475449fc-d6gdj: {kubelet capz-conf-whcdvl-control-plane-2s6hv} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "1400f633e18fcd86394a2e41ec0c4b9bf6593bd83c510846035aaaf53b14be65": 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 11 16:40:36.376: INFO: At 2022-11-11 16:26:31 +0000 UTC - event for coredns-64475449fc-wn4xw: {kubelet capz-conf-whcdvl-control-plane-2s6hv} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "58ebe2d5dba64d455abf58858b670c3e3d261c22decdba15e96a6398ac0524ed": 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 11 16:40:36.376: INFO: At 2022-11-11 16:26:31 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {kubelet capz-conf-whcdvl-control-plane-2s6hv} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b7c36aed6b449f207030b40f1987192e4b7598750a161871974e17ea72146876": 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 11 16:40:36.376: INFO: At 2022-11-11 16:26:40 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.670717216s (9.670739918s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:40 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container calico-node
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:41 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container calico-node
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:41 +0000 UTC - event for calico-node-bf56r: {kubelet capz-conf-whcdvl-control-plane-2s6hv} 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 11 16:40:36.376: INFO: At 2022-11-11 16:26:44 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:44 +0000 UTC - event for coredns-64475449fc-d6gdj: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:44 +0000 UTC - event for coredns-64475449fc-d6gdj: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container coredns
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:44 +0000 UTC - event for coredns-64475449fc-d6gdj: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container coredns
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:45 +0000 UTC - event for coredns-64475449fc-d6gdj: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Unhealthy: Readiness probe failed: Get "http://192.168.34.1:8181/ready": dial tcp 192.168.34.1:8181: connect: connection refused
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:46 +0000 UTC - event for coredns-64475449fc-wn4xw: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container coredns
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:46 +0000 UTC - event for coredns-64475449fc-wn4xw: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:46 +0000 UTC - event for coredns-64475449fc-wn4xw: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container coredns
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:47 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:53 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 8.846519687s (8.84681089s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:53 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container calico-kube-controllers
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:53 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-p52w5: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container calico-kube-controllers
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:57 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.209719766s (10.118696462s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:57 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Created: Created container metrics-server
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:26:58 +0000 UTC - event for metrics-server-954b56d74-6dtnh: {kubelet capz-conf-whcdvl-control-plane-2s6hv} Started: Started container metrics-server
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:56 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-h8xjm
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:56 +0000 UTC - event for calico-node-windows-h8xjm: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-h8xjm to capz-conf-5sjnx
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:56 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-mgzj2
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:56 +0000 UTC - event for containerd-logger-mgzj2: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-mgzj2 to capz-conf-5sjnx
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:56 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-mltkt
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:56 +0000 UTC - event for kube-proxy-windows-mltkt: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-mltkt to capz-conf-5sjnx
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:58 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:28:58 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:04 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-8jqjt
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:04 +0000 UTC - event for calico-node-windows-8jqjt: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-8jqjt to capz-conf-2vrxv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:04 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-x7ml5
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:04 +0000 UTC - event for containerd-logger-x7ml5: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-x7ml5 to capz-conf-2vrxv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:04 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-mdzbf
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:04 +0000 UTC - event for kube-proxy-windows-mdzbf: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-mdzbf to capz-conf-2vrxv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:06 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} FailedMount: MountVolume.SetUp failed for volume "calico-config-windows" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:06 +0000 UTC - event for containerd-logger-x7ml5: {kubelet capz-conf-2vrxv} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:13 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:13 +0000 UTC - event for containerd-logger-mgzj2: {kubelet capz-conf-5sjnx} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:13 +0000 UTC - event for kube-proxy-windows-mltkt: {kubelet capz-conf-5sjnx} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.15_cc704f97784c33-calico-hostprocess" already present on machine
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:14 +0000 UTC - event for kube-proxy-windows-mltkt: {kubelet capz-conf-5sjnx} Created: Created container kube-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:14 +0000 UTC - event for kube-proxy-windows-mltkt: {kubelet capz-conf-5sjnx} Started: Started container kube-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:18 +0000 UTC - event for containerd-logger-mgzj2: {kubelet capz-conf-5sjnx} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.8834246s (4.8834246s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:23 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:23 +0000 UTC - event for containerd-logger-x7ml5: {kubelet capz-conf-2vrxv} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:23 +0000 UTC - event for kube-proxy-windows-mdzbf: {kubelet capz-conf-2vrxv} Started: Started container kube-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:23 +0000 UTC - event for kube-proxy-windows-mdzbf: {kubelet capz-conf-2vrxv} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.15_cc704f97784c33-calico-hostprocess" already present on machine
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:23 +0000 UTC - event for kube-proxy-windows-mdzbf: {kubelet capz-conf-2vrxv} Created: Created container kube-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:24 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.7235059s (10.5344313s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:24 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Created: Created container install-cni
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:24 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Started: Started container install-cni
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:24 +0000 UTC - event for containerd-logger-mgzj2: {kubelet capz-conf-5sjnx} Started: Started container containerd-logger
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:24 +0000 UTC - event for containerd-logger-mgzj2: {kubelet capz-conf-5sjnx} Created: Created container containerd-logger
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:26 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-c4ffc
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:26 +0000 UTC - event for csi-proxy-c4ffc: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-c4ffc to capz-conf-5sjnx
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:27 +0000 UTC - event for csi-proxy-c4ffc: {kubelet capz-conf-5sjnx} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:28 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Created: Created container install-cni
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:28 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.4167961s (5.417098s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:29 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Started: Started container install-cni
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:30 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:30 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-jd6td
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:30 +0000 UTC - event for csi-proxy-jd6td: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-jd6td to capz-conf-2vrxv
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:31 +0000 UTC - event for csi-proxy-jd6td: {kubelet capz-conf-2vrxv} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:32 +0000 UTC - event for containerd-logger-x7ml5: {kubelet capz-conf-2vrxv} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.3250609s (9.7129272s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:34 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:39 +0000 UTC - event for containerd-logger-x7ml5: {kubelet capz-conf-2vrxv} Created: Created container containerd-logger
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:40 +0000 UTC - event for containerd-logger-x7ml5: {kubelet capz-conf-2vrxv} Started: Started container containerd-logger
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:46 +0000 UTC - event for csi-proxy-c4ffc: {kubelet capz-conf-5sjnx} Created: Created container csi-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:46 +0000 UTC - event for csi-proxy-c4ffc: {kubelet capz-conf-5sjnx} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 19.3874399s (19.3877473s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:47 +0000 UTC - event for csi-proxy-c4ffc: {kubelet capz-conf-5sjnx} Started: Started container csi-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:50 +0000 UTC - event for csi-proxy-jd6td: {kubelet capz-conf-2vrxv} Created: Created container csi-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:50 +0000 UTC - event for csi-proxy-jd6td: {kubelet capz-conf-2vrxv} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 17.818441s (19.6961374s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:51 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:51 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Started: Started container calico-node-startup
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:51 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Created: Created container calico-node-startup
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:51 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.4890257s (20.6520234s including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:51 +0000 UTC - event for csi-proxy-jd6td: {kubelet capz-conf-2vrxv} Started: Started container csi-proxy
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:52 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 961.5016ms (961.5016ms including waiting)
Nov 11 16:40:36.376: INFO: At 2022-11-11 16:29:55 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.6338008s (21.2477622s including waiting)
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:29:55 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Created: Created container calico-node-startup
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:29:55 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Started: Started container calico-node-startup
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:29:55 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:29:56 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 965.1091ms (965.1091ms including waiting)
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:29:58 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Created: Created container calico-node-felix
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:29:58 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Started: Started container calico-node-felix
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:30:02 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Created: Created container calico-node-felix
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:30:03 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Started: Started container calico-node-felix
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:30:19 +0000 UTC - event for calico-node-windows-h8xjm: {kubelet capz-conf-5sjnx} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 956.3072ms (956.3072ms including waiting)
Nov 11 16:40:36.377: INFO: At 2022-11-11 16:30:24 +0000 UTC - event for calico-node-windows-8jqjt: {kubelet capz-conf-2vrxv} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 946.9276ms (946.9276ms including waiting)
Nov 11 16:40:36.538: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 16:40:36.538: INFO: calico-kube-controllers-56c5ff4bf8-p52w5 capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:54 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC }]
Nov 11 16:40:36.538: INFO: calico-node-bf56r capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:31 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:15 +0000 UTC }]
Nov 11 16:40:36.538: INFO: calico-node-windows-8jqjt capz-conf-2vrxv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:30:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:30:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:04 +0000 UTC }]
Nov 11 16:40:36.538: INFO: calico-node-windows-h8xjm capz-conf-5sjnx Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:30:26 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:30:26 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:28:56 +0000 UTC }]
Nov 11 16:40:36.538: INFO: containerd-logger-mgzj2 capz-conf-5sjnx Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:28:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:25 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:25 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:28:56 +0000 UTC }]
Nov 11 16:40:36.538: INFO: containerd-logger-x7ml5 capz-conf-2vrxv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:04 +0000 UTC }]
Nov 11 16:40:36.538: INFO: coredns-64475449fc-d6gdj capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC }]
Nov 11 16:40:36.538: INFO: coredns-64475449fc-wn4xw capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC }]
Nov 11 16:40:36.538: INFO: csi-proxy-c4ffc capz-conf-5sjnx Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:26 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:26 +0000 UTC }]
Nov 11 16:40:36.538: INFO: csi-proxy-jd6td capz-conf-2vrxv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:30 +0000 UTC }]
Nov 11 16:40:36.538: INFO: etcd-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:47 +0000 UTC }]
Nov 11 16:40:36.538: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:36.538: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:36.538: INFO: kube-proxy-windows-mdzbf capz-conf-2vrxv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:04 +0000 UTC }]
Nov 11 16:40:36.538: INFO: kube-proxy-windows-mltkt capz-conf-5sjnx Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:28:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:14 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:29:14 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:28:56 +0000 UTC }]
Nov 11 16:40:36.538: INFO: kube-proxy-x8c7k capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:49 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:57 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:25:49 +0000 UTC }]
Nov 11 16:40:36.538: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Nov 11 16:40:36.538: INFO: metrics-server-954b56d74-6dtnh capz-conf-whcdvl-control-plane-2s6hv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:27:21 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:27:21 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 16:26:30 +0000 UTC }]
Nov 11 16:40:36.538: INFO:
Nov 11 16:40:37.671: INFO:
Logging node info for node capz-conf-2vrxv
Nov 11 16:40:37.792: INFO: Node Info: &Node{ObjectMeta:{capz-conf-2vrxv 89a2a472-bad2-4ec0-9954-85d0e8a7997d 2099 0 2022-11-11 16:29:04 +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:westeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-2vrxv kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:westeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-whcdvl cluster.x-k8s.io/cluster-namespace:capz-conf-whcdvl cluster.x-k8s.io/machine:capz-conf-whcdvl-md-win-97d888444-n64zw cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-whcdvl-md-win-97d888444 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.33.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:c2:55:51 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-11 16:29:04 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-11 16:29:04 +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-11 16:29:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2022-11-11 16:30:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {manager Update v1 2022-11-11 16:30:31 +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":{}}}} } {kubelet.exe Update v1 2022-11-11 16:40:17 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-whcdvl/providers/Microsoft.Compute/virtualMachines/capz-conf-2vrxv,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-11 16:40:17 +0000 UTC,LastTransitionTime:2022-11-11 16:29:04 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-11 16:40:17 +0000 UTC,LastTransitionTime:2022-11-11 16:29:04 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-11 16:40:17 +0000 UTC,LastTransitionTime:2022-11-11 16:29:04 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-11 16:40:17 +0000 UTC,LastTransitionTime:2022-11-11 16:29:30 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-2vrxv,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-2vrxv,SystemUUID:545BC61E-4EB7-4015-A628-7B4D5B506460,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.51+013c1ef249fd5d-dirty,KubeProxyVersion:v1.26.0-beta.0.51+013c1ef249fd5d-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.15_cc704f97784c33-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 11 16:40:37.792: INFO:
Logging kubelet events for node capz-conf-2vrxv
Nov 11 16:40:37.902: INFO:
Logging pods the kubelet thinks is on node capz-conf-2vrxv
Nov 11 16:40:38.167: INFO: containerd-logger-x7ml5 started at 2022-11-11 16:29:05 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:38.167: INFO: Container containerd-logger ready: true, restart count 0
Nov 11 16:40:38.167: INFO: kube-proxy-windows-mdzbf started at 2022-11-11 16:29:05 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:38.167: INFO: Container kube-proxy ready: true, restart count 0
Nov 11 16:40:38.167: INFO: csi-proxy-jd6td started at 2022-11-11 16:29:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:38.167: INFO: Container csi-proxy ready: true, restart count 0
Nov 11 16:40:38.167: INFO: calico-node-windows-8jqjt started at 2022-11-11 16:29:05 +0000 UTC (1+2 container statuses recorded)
Nov 11 16:40:38.167: INFO: Init container install-cni ready: true, restart count 0
Nov 11 16:40:38.167: INFO: Container calico-node-felix ready: true, restart count 1
Nov 11 16:40:38.167: INFO: Container calico-node-startup ready: true, restart count 0
Nov 11 16:40:38.664: INFO:
Latency metrics for node capz-conf-2vrxv
Nov 11 16:40:38.664: INFO:
Logging node info for node capz-conf-5sjnx
Nov 11 16:40:38.783: INFO: Node Info: &Node{ObjectMeta:{capz-conf-5sjnx fad2c6d1-6387-4c17-a916-afabb87c537b 2087 0 2022-11-11 16:28:56 +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:westeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-5sjnx kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:westeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-whcdvl cluster.x-k8s.io/cluster-namespace:capz-conf-whcdvl cluster.x-k8s.io/machine:capz-conf-whcdvl-md-win-97d888444-27hkb cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-whcdvl-md-win-97d888444 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.154.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:2d:49:20 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-11 16:28:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-11 16:28:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f: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-11 16:29:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2022-11-11 16:30:16 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {manager Update v1 2022-11-11 16:30:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kubelet.exe Update v1 2022-11-11 16:40:10 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-whcdvl/providers/Microsoft.Compute/virtualMachines/capz-conf-5sjnx,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-11 16:40:10 +0000 UTC,LastTransitionTime:2022-11-11 16:28:56 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-11 16:40:10 +0000 UTC,LastTransitionTime:2022-11-11 16:28:56 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-11 16:40:10 +0000 UTC,LastTransitionTime:2022-11-11 16:28:56 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-11 16:40:10 +0000 UTC,LastTransitionTime:2022-11-11 16:29:26 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-5sjnx,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-5sjnx,SystemUUID:5F11AC40-C355-4EE8-AAD2-2D7F83E0D1BF,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.51+013c1ef249fd5d-dirty,KubeProxyVersion:v1.26.0-beta.0.51+013c1ef249fd5d-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.15_cc704f97784c33-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 11 16:40:38.783: INFO:
Logging kubelet events for node capz-conf-5sjnx
Nov 11 16:40:38.893: INFO:
Logging pods the kubelet thinks is on node capz-conf-5sjnx
Nov 11 16:40:39.057: INFO: kube-proxy-windows-mltkt started at 2022-11-11 16:28:57 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.057: INFO: Container kube-proxy ready: true, restart count 0
Nov 11 16:40:39.057: INFO: csi-proxy-c4ffc started at 2022-11-11 16:29:26 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.057: INFO: Container csi-proxy ready: true, restart count 0
Nov 11 16:40:39.057: INFO: calico-node-windows-h8xjm started at 2022-11-11 16:28:57 +0000 UTC (1+2 container statuses recorded)
Nov 11 16:40:39.057: INFO: Init container install-cni ready: true, restart count 0
Nov 11 16:40:39.057: INFO: Container calico-node-felix ready: true, restart count 1
Nov 11 16:40:39.057: INFO: Container calico-node-startup ready: true, restart count 0
Nov 11 16:40:39.057: INFO: containerd-logger-mgzj2 started at 2022-11-11 16:28:57 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.057: INFO: Container containerd-logger ready: true, restart count 0
Nov 11 16:40:39.520: INFO:
Latency metrics for node capz-conf-5sjnx
Nov 11 16:40:39.520: INFO:
Logging node info for node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:39.644: INFO: Node Info: &Node{ObjectMeta:{capz-conf-whcdvl-control-plane-2s6hv 2671018f-7e42-4a6b-8565-6259f9523f80 1850 0 2022-11-11 16:25:40 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:westeurope failure-domain.beta.kubernetes.io/zone:westeurope-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-whcdvl-control-plane-2s6hv 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:westeurope topology.kubernetes.io/zone:westeurope-1] map[cluster.x-k8s.io/cluster-name:capz-conf-whcdvl cluster.x-k8s.io/cluster-namespace:capz-conf-whcdvl cluster.x-k8s.io/machine:capz-conf-whcdvl-control-plane-d84wz cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-whcdvl-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.34.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-11 16:25:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-11 16:25:45 +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-11 16:26:10 +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-11 16:26:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-11 16:26:41 +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-11 16:37:31 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-whcdvl/providers/Microsoft.Compute/virtualMachines/capz-conf-whcdvl-control-plane-2s6hv,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-11 16:26:41 +0000 UTC,LastTransitionTime:2022-11-11 16:26:41 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-11 16:37:31 +0000 UTC,LastTransitionTime:2022-11-11 16:25:40 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-11 16:37:31 +0000 UTC,LastTransitionTime:2022-11-11 16:25:40 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-11 16:37:31 +0000 UTC,LastTransitionTime:2022-11-11 16:25:40 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-11 16:37:31 +0000 UTC,LastTransitionTime:2022-11-11 16:26:30 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-whcdvl-control-plane-2s6hv,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:4027434049ae46778e825c61234916fb,SystemUUID:5d399d58-e52b-e246-aa54-6c5381e096d8,BootID:80077b28-1899-4d00-970d-9cc76f3e7c6e,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.51+013c1ef249fd5d,KubeProxyVersion:v1.26.0-beta.0.51+013c1ef249fd5d,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:1ea2af00fd3519fa458cf3dbcda23fc367a81cada6190417933caa6b34659ec3 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.15_cc704f97784c33],SizeBytes:35104220,},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:d152cf6e121a433bbadfd82b8e33f0667f75146b55d04d721aed1660bf14fe4a gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.15_cc704f97784c33],SizeBytes:32080902,},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:2c3e7c2afc88024b5b8ead8260810319f76660a9a493092ad12402f1c8a6159a capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.51_013c1ef249fd5d],SizeBytes:21533145,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:d8efc1f16009891f595089e3218ba4247b38b0b2678a3144ac4764840b80448b gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.15_cc704f97784c33],SizeBytes:21418933,},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:018cda1efad5e9ede1cf6b3376f91569f3ec472fed15023294f49c348b2ed616 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.15_cc704f97784c33],SizeBytes:17334234,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 11 16:40:39.645: INFO:
Logging kubelet events for node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:39.755: INFO:
Logging pods the kubelet thinks is on node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:39.978: INFO: calico-kube-controllers-56c5ff4bf8-p52w5 started at 2022-11-11 16:26:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 11 16:40:39.978: INFO: etcd-capz-conf-whcdvl-control-plane-2s6hv started at 2022-11-11 16:25:47 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Container etcd ready: true, restart count 0
Nov 11 16:40:39.978: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv started at <nil> (0+0 container statuses recorded)
Nov 11 16:40:39.978: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv started at <nil> (0+0 container statuses recorded)
Nov 11 16:40:39.978: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv started at <nil> (0+0 container statuses recorded)
Nov 11 16:40:39.978: INFO: coredns-64475449fc-d6gdj started at 2022-11-11 16:26:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Container coredns ready: true, restart count 0
Nov 11 16:40:39.978: INFO: kube-proxy-x8c7k started at 2022-11-11 16:25:49 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Container kube-proxy ready: true, restart count 0
Nov 11 16:40:39.978: INFO: calico-node-bf56r started at 2022-11-11 16:26:15 +0000 UTC (2+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 11 16:40:39.978: INFO: Init container install-cni ready: true, restart count 0
Nov 11 16:40:39.978: INFO: Container calico-node ready: true, restart count 0
Nov 11 16:40:39.978: INFO: metrics-server-954b56d74-6dtnh started at 2022-11-11 16:26:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Container metrics-server ready: true, restart count 0
Nov 11 16:40:39.978: INFO: coredns-64475449fc-wn4xw started at 2022-11-11 16:26:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 16:40:39.978: INFO: Container coredns ready: true, restart count 0
Nov 11 16:40:40.401: INFO:
Latency metrics for node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:40.537: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 11 16:40:40.756: INFO: Failed to get logs of pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv)
Nov 11 16:40:40.756: INFO: Logs of kube-system/kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv:kube-apiserver on node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:40.756: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv:kube-apiserver
Nov 11 16:40:40.980: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv)
Nov 11 16:40:40.980: INFO: Logs of kube-system/kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv:kube-controller-manager on node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:40.980: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv:kube-controller-manager
Nov 11 16:40:41.367: INFO: Failed to get logs of pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv)
Nov 11 16:40:41.367: INFO: Logs of kube-system/kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv:kube-scheduler on node capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:40:41.368: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv:kube-scheduler
Nov 11 16:40:41.368: 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-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:248 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:80 +0x8f
reflect.Value.call({0x669b980?, 0x7885858?, 0xc0000a46b0?}, {0x75a7cb6, 0x4}, {0xc0000b7f20, 0x0, 0xc0000a46f8?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x669b980?, 0x7885858?, 0x268587b?}, {0xc0000b7f20?, 0x200000003?, 0xc0000061a0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
�[38;5;243m<< End Captured GinkgoWriter Output�[0m
�[38;5;9mNov 11 16:40:41.368: 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-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending []
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:248�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.933 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:76�[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:76�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.906 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:76�[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:76�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.907 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:76�[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:76�[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:76�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:76�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:76�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:248�[0m
�[38;5;9m�[1mRan 0 of 6812 Specs in 606.990 seconds�[0m
�[38;5;9m�[1mFAIL!�[0m -- �[38;5;14m�[1mA BeforeSuite node failed so all tests were skipped.�[0m
I1111 16:30:34.163550 15 e2e.go:125] Starting e2e run "d2fcf2f8-6eed-44f6-b911-3639c9ee167e" 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 (607.33s)
FAIL
I1111 16:30:34.162813 16 e2e.go:125] Starting e2e run "16211b50-7fe0-46d8-a4f3-504baad823a0" 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 (607.26s)
FAIL
I1111 16:30:34.159330 18 e2e.go:125] Starting e2e run "9639ceb8-db5d-4619-a60f-404f2849d9ce" 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 (607.26s)
FAIL
I1111 16:30:34.159726 20 e2e.go:125] Starting e2e run "cd4e83e4-233d-41d4-ac7f-94fb8b942480" 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 (607.26s)
FAIL
Ginkgo ran 1 suite in 10m7.485681878s
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 11 16:40:42.209: INFO: FAILED!
Nov 11 16:40:42.209: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
�[1mSTEP�[0m: Dumping logs from the "capz-conf-whcdvl" workload cluster
�[1mSTEP�[0m: Dumping workload cluster capz-conf-whcdvl/capz-conf-whcdvl logs
Nov 11 16:40:42.282: INFO: Collecting logs for Linux node capz-conf-whcdvl-control-plane-2s6hv in cluster capz-conf-whcdvl in namespace capz-conf-whcdvl
Nov 11 16:41:00.479: INFO: Collecting boot logs for AzureMachine capz-conf-whcdvl-control-plane-2s6hv
Nov 11 16:41:02.125: INFO: Collecting logs for Windows node capz-conf-5sjnx in cluster capz-conf-whcdvl in namespace capz-conf-whcdvl
Nov 11 16:43:36.450: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-5sjnx to /logs/artifacts/clusters/capz-conf-whcdvl/machines/capz-conf-whcdvl-md-win-97d888444-27hkb/crashdumps.tar
Nov 11 16:43:39.958: INFO: Collecting boot logs for AzureMachine capz-conf-whcdvl-md-win-5sjnx
Nov 11 16:43:41.254: INFO: Collecting logs for Windows node capz-conf-2vrxv in cluster capz-conf-whcdvl in namespace capz-conf-whcdvl
Nov 11 16:46:17.119: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-2vrxv to /logs/artifacts/clusters/capz-conf-whcdvl/machines/capz-conf-whcdvl-md-win-97d888444-n64zw/crashdumps.tar
Nov 11 16:46:20.698: INFO: Collecting boot logs for AzureMachine capz-conf-whcdvl-md-win-2vrxv
�[1mSTEP�[0m: Dumping workload cluster capz-conf-whcdvl/capz-conf-whcdvl kube-system pod logs
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-kube-controllers-56c5ff4bf8-p52w5, container calico-kube-controllers
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-windows-8jqjt
�[1mSTEP�[0m: Collecting events for Pod kube-system/metrics-server-954b56d74-6dtnh
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-windows-mdzbf
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-bf56r
�[1mSTEP�[0m: Collecting events for Pod kube-system/containerd-logger-x7ml5
�[1mSTEP�[0m: Collecting events for Pod kube-system/csi-proxy-jd6td
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-8jqjt, container calico-node-startup
�[1mSTEP�[0m: Fetching kube-system pod logs took 1.164283846s
�[1mSTEP�[0m: Dumping workload cluster capz-conf-whcdvl/capz-conf-whcdvl Azure activity log
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-64475449fc-d6gdj, container coredns
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-kube-controllers-56c5ff4bf8-p52w5
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-mltkt, container kube-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-bf56r, container calico-node
�[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-conf-whcdvl-control-plane-2s6hv, container etcd
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-h8xjm, container calico-node-startup
�[1mSTEP�[0m: Collecting events for Pod kube-system/coredns-64475449fc-d6gdj
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-8jqjt, container calico-node-felix
�[1mSTEP�[0m: Creating log watcher for controller kube-system/csi-proxy-jd6td, container csi-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-windows-mltkt
�[1mSTEP�[0m: Creating log watcher for controller kube-system/csi-proxy-c4ffc, container csi-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-64475449fc-wn4xw, container coredns
�[1mSTEP�[0m: Collecting events for Pod kube-system/csi-proxy-c4ffc
�[1mSTEP�[0m: Collecting events for Pod kube-system/etcd-capz-conf-whcdvl-control-plane-2s6hv
�[1mSTEP�[0m: failed to find events of Pod "etcd-capz-conf-whcdvl-control-plane-2s6hv"
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv, container kube-apiserver
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-x8c7k, container kube-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/coredns-64475449fc-wn4xw
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-h8xjm, container calico-node-felix
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-x8c7k
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-windows-h8xjm
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv, container kube-scheduler
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv, container kube-controller-manager
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-mdzbf, container kube-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/containerd-logger-mgzj2
�[1mSTEP�[0m: Creating log watcher for controller kube-system/containerd-logger-x7ml5, container containerd-logger
�[1mSTEP�[0m: Creating log watcher for controller kube-system/containerd-logger-mgzj2, container containerd-logger
�[1mSTEP�[0m: Creating log watcher for controller kube-system/metrics-server-954b56d74-6dtnh, container metrics-server
�[1mSTEP�[0m: failed to find events of Pod "kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv"
�[1mSTEP�[0m: failed to find events of Pod "kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv"
�[1mSTEP�[0m: failed to find events of Pod "kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv"
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv" is not available
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv, container kube-controller-manager: container "kube-controller-manager" in pod "kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv" is not available
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv, container kube-scheduler: container "kube-scheduler" in pod "kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv" is not available
�[1mSTEP�[0m: Fetching activity logs took 3.503930167s
Nov 11 16:46:26.738: INFO: Dumping all the Cluster API resources in the "capz-conf-whcdvl" namespace
Nov 11 16:46:27.137: INFO: Deleting all clusters in the capz-conf-whcdvl namespace
�[1mSTEP�[0m: Deleting cluster capz-conf-whcdvl
INFO: Waiting for the Cluster capz-conf-whcdvl/capz-conf-whcdvl to be deleted
�[1mSTEP�[0m: Waiting for cluster capz-conf-whcdvl to be deleted
Nov 11 16:54:17.523: INFO: Deleting namespace used for hosting the "conformance-tests" test spec
INFO: Deleting namespace capz-conf-whcdvl
Nov 11 16:54:17.551: INFO: Checking if any resources are left over in Azure for spec "conformance-tests"
�[1mSTEP�[0m: Redacting sensitive information from logs
from junit.e2e_suite.1.xml
Filter through log files | View test history on testgrid
capz-e2e Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider
... skipping 115 lines ... /home/prow/go/src/k8s.io/kubernetes /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 138 100 138 0 0 5750 0 --:--:-- --:--:-- --:--:-- 5750 100 32 100 32 0 0 450 0 --:--:-- --:--:-- --:--:-- 450 Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.26.0-beta.0.51_013c1ef249fd5d not found: manifest unknown: manifest tagged by "v1.26.0-beta.0.51_013c1ef249fd5d" is not found Building Kubernetes make: Entering directory '/home/prow/go/src/k8s.io/kubernetes' +++ [1111 15:48:30] Verifying Prerequisites.... +++ [1111 15:48:30] Building Docker image kube-build:build-5836d4e437-5-v1.25.0-go1.19.3-bullseye.0 +++ [1111 15:51:17] Creating data container kube-build-data-5836d4e437-5-v1.25.0-go1.19.3-bullseye.0 +++ [1111 15:51:41] Syncing sources to container ... skipping 720 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-whcdvl [1mSTEP[0m: Creating namespace "capz-conf-whcdvl" for hosting the cluster Nov 11 16:20:38.739: INFO: starting to create namespace for hosting the "capz-conf-whcdvl" test spec 2022/11/11 16:20:38 failed trying to get namespace (capz-conf-whcdvl):namespaces "capz-conf-whcdvl" not found INFO: Creating namespace capz-conf-whcdvl INFO: Creating event watcher for namespace "capz-conf-whcdvl" [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-whcdvl" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.26.0-beta.0.15+cc704f97784c33, 1 control-plane machines, 0 worker machines) INFO: Getting the cluster template yaml ... skipping 41 lines ... ==================================================== Random Seed: [1m1668184234[0m - will randomize all specs Will run [1m339[0m of [1m6812[0m specs Running in parallel across [1m4[0m processes [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.863 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:76[0m [38;5;243mBegin Captured GinkgoWriter Output >>[0m [SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:76 Nov 11 16:30:34.507: INFO: >>> kubeConfig: /tmp/kubeconfig Nov 11 16:30:34.509: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Nov 11 16:30:35.013: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Nov 11 16:30:35.411: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:35.411: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:35.411: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:35.411: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Nov 11 16:30:35.411: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:35.411: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:35.411: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:35.411: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:35.411: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:35.411: INFO: Nov 11 16:30:37.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:37.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:37.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:37.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Nov 11 16:30:37.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:37.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:37.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:37.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:37.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:37.805: INFO: Nov 11 16:30:39.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:39.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:39.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:39.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Nov 11 16:30:39.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:39.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:39.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:39.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:39.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:39.806: INFO: Nov 11 16:30:41.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:41.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:41.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:41.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Nov 11 16:30:41.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:41.819: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:41.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:41.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:41.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:41.819: INFO: Nov 11 16:30:43.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:43.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:43.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:43.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Nov 11 16:30:43.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:43.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:43.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:43.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:43.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:43.806: INFO: Nov 11 16:30:45.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:45.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:45.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:45.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Nov 11 16:30:45.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:45.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:45.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:45.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:45.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:45.805: INFO: Nov 11 16:30:47.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:47.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:47.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:47.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Nov 11 16:30:47.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:47.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:47.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:47.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:47.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:47.805: INFO: Nov 11 16:30:49.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:49.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:49.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:49.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Nov 11 16:30:49.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:49.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:49.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:49.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:49.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:49.805: INFO: Nov 11 16:30:51.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:51.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:51.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:51.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Nov 11 16:30:51.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:51.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:51.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:51.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:51.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:51.810: INFO: Nov 11 16:30:53.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:53.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:53.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:53.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Nov 11 16:30:53.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:53.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:53.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:53.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:53.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:53.804: INFO: Nov 11 16:30:55.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:55.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:55.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:55.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Nov 11 16:30:55.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:55.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:55.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:55.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:55.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:55.806: INFO: Nov 11 16:30:57.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:57.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:57.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:57.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Nov 11 16:30:57.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:57.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:57.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:57.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:57.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:57.805: INFO: Nov 11 16:30:59.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:59.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:59.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:30:59.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Nov 11 16:30:59.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:30:59.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:30:59.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:59.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:59.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:30:59.805: INFO: Nov 11 16:31:01.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:01.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:01.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:01.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Nov 11 16:31:01.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:01.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:01.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:01.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:01.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:01.805: INFO: Nov 11 16:31:03.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:03.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:03.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:03.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Nov 11 16:31:03.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:03.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:03.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:03.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:03.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:03.804: INFO: Nov 11 16:31:05.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:05.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:05.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:05.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Nov 11 16:31:05.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:05.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:05.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:05.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:05.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:05.808: INFO: Nov 11 16:31:07.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:07.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:07.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:07.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Nov 11 16:31:07.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:07.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:07.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:07.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:07.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:07.805: INFO: Nov 11 16:31:09.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:09.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:09.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:09.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Nov 11 16:31:09.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:09.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:09.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:09.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:09.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:09.806: INFO: Nov 11 16:31:11.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:11.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:11.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:11.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Nov 11 16:31:11.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:11.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:11.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:11.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:11.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:11.808: INFO: Nov 11 16:31:13.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:13.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:13.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:13.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Nov 11 16:31:13.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:13.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:13.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:13.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:13.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:13.807: INFO: Nov 11 16:31:15.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:15.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:15.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:15.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Nov 11 16:31:15.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:15.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:15.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:15.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:15.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:15.809: INFO: Nov 11 16:31:17.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:17.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:17.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:17.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Nov 11 16:31:17.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:17.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:17.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:17.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:17.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:17.804: INFO: Nov 11 16:31:19.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:19.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:19.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:19.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Nov 11 16:31:19.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:19.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:19.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:19.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:19.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:19.808: INFO: Nov 11 16:31:21.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:21.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:21.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:21.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Nov 11 16:31:21.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:21.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:21.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:21.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:21.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:21.807: INFO: Nov 11 16:31:23.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:23.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:23.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:23.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Nov 11 16:31:23.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:23.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:23.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:23.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:23.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:23.804: INFO: Nov 11 16:31:25.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:25.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:25.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:25.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Nov 11 16:31:25.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:25.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:25.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:25.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:25.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:25.807: INFO: Nov 11 16:31:27.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:27.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:27.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:27.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Nov 11 16:31:27.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:27.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:27.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:27.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:27.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:27.804: INFO: Nov 11 16:31:29.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:29.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:29.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:29.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Nov 11 16:31:29.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:29.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:29.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:29.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:29.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:29.807: INFO: Nov 11 16:31:31.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:31.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:31.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:31.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Nov 11 16:31:31.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:31.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:31.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:31.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:31.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:31.808: INFO: Nov 11 16:31:33.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:33.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:33.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:33.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Nov 11 16:31:33.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:33.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:33.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:33.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:33.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:33.807: INFO: Nov 11 16:31:35.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:35.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:35.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:35.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Nov 11 16:31:35.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:35.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:35.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:35.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:35.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:35.810: INFO: Nov 11 16:31:37.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:37.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:37.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:37.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Nov 11 16:31:37.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:37.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:37.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:37.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:37.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:37.804: INFO: Nov 11 16:31:39.830: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:39.830: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:39.830: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:39.830: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Nov 11 16:31:39.830: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:39.830: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:39.830: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:39.830: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:39.830: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:39.830: INFO: Nov 11 16:31:41.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:41.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:41.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:41.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Nov 11 16:31:41.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:41.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:41.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:41.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:41.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:41.806: INFO: Nov 11 16:31:43.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:43.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:43.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:43.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Nov 11 16:31:43.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:43.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:43.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:43.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:43.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:43.808: INFO: Nov 11 16:31:45.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:45.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:45.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:45.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Nov 11 16:31:45.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:45.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:45.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:45.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:45.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:45.816: INFO: Nov 11 16:31:47.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:47.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:47.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:47.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Nov 11 16:31:47.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:47.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:47.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:47.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:47.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:47.806: INFO: Nov 11 16:31:49.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:49.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:49.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:49.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Nov 11 16:31:49.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:49.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:49.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:49.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:49.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:49.806: INFO: Nov 11 16:31:51.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:51.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:51.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:51.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Nov 11 16:31:51.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:51.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:51.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:51.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:51.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:51.804: INFO: Nov 11 16:31:53.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:53.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:53.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:53.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Nov 11 16:31:53.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:53.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:53.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:53.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:53.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:53.807: INFO: Nov 11 16:31:55.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:55.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:55.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:55.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Nov 11 16:31:55.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:55.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:55.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:55.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:55.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:55.808: INFO: Nov 11 16:31:57.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:57.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:57.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:57.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Nov 11 16:31:57.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:57.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:57.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:57.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:57.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:57.807: INFO: Nov 11 16:31:59.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:59.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:59.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:31:59.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Nov 11 16:31:59.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:31:59.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:31:59.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:59.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:59.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:31:59.808: INFO: Nov 11 16:32:01.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:01.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:01.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:01.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Nov 11 16:32:01.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:01.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:01.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:01.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:01.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:01.807: INFO: Nov 11 16:32:03.995: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:03.995: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:03.995: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:03.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Nov 11 16:32:03.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:03.995: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:03.995: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:03.995: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:03.995: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:03.995: INFO: Nov 11 16:32:05.852: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:05.852: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:05.852: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:05.852: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Nov 11 16:32:05.852: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:05.852: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:05.852: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:05.852: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:05.852: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:05.852: INFO: Nov 11 16:32:07.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:07.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:07.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:07.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Nov 11 16:32:07.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:07.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:07.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:07.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:07.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:07.805: INFO: Nov 11 16:32:09.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:09.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:09.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:09.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Nov 11 16:32:09.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:09.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:09.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:09.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:09.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:09.805: INFO: Nov 11 16:32:11.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:11.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:11.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:11.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Nov 11 16:32:11.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:11.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:11.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:11.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:11.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:11.807: INFO: Nov 11 16:32:13.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:13.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:13.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:13.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Nov 11 16:32:13.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:13.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:13.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:13.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:13.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:13.814: INFO: Nov 11 16:32:15.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:15.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:15.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:15.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Nov 11 16:32:15.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:15.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:15.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:15.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:15.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:15.810: INFO: Nov 11 16:32:17.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:17.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:17.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:17.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Nov 11 16:32:17.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:17.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:17.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:17.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:17.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:17.805: INFO: Nov 11 16:32:19.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:19.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:19.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:19.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Nov 11 16:32:19.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:19.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:19.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:19.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:19.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:19.816: INFO: Nov 11 16:32:21.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:21.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:21.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:21.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Nov 11 16:32:21.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:21.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:21.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:21.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:21.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:21.806: INFO: Nov 11 16:32:23.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:23.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:23.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:23.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Nov 11 16:32:23.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:23.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:23.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:23.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:23.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:23.809: INFO: Nov 11 16:32:25.869: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:25.869: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:25.869: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:25.869: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Nov 11 16:32:25.869: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:25.869: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:25.869: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:25.869: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:25.869: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:25.869: INFO: Nov 11 16:32:27.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:27.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:27.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:27.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Nov 11 16:32:27.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:27.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:27.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:27.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:27.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:27.808: INFO: Nov 11 16:32:29.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:29.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:29.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:29.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Nov 11 16:32:29.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:29.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:29.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:29.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:29.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:29.813: INFO: Nov 11 16:32:31.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:31.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:31.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:31.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Nov 11 16:32:31.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:31.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:31.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:31.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:31.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:31.808: INFO: Nov 11 16:32:33.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:33.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:33.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:33.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Nov 11 16:32:33.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:33.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:33.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:33.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:33.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:33.810: INFO: Nov 11 16:32:35.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:35.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:35.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:35.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Nov 11 16:32:35.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:35.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:35.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:35.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:35.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:35.813: INFO: Nov 11 16:32:37.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:37.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:37.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:37.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Nov 11 16:32:37.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:37.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:37.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:37.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:37.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:37.818: INFO: Nov 11 16:32:39.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:39.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:39.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:39.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Nov 11 16:32:39.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:39.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:39.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:39.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:39.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:39.807: INFO: Nov 11 16:32:41.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:41.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:41.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:41.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Nov 11 16:32:41.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:41.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:41.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:41.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:41.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:41.807: INFO: Nov 11 16:32:43.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:43.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:43.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:43.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Nov 11 16:32:43.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:43.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:43.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:43.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:43.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:43.806: INFO: Nov 11 16:32:45.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:45.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:45.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:45.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Nov 11 16:32:45.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:45.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:45.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:45.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:45.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:45.820: INFO: Nov 11 16:32:47.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:47.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:47.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:47.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Nov 11 16:32:47.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:47.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:47.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:47.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:47.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:47.807: INFO: Nov 11 16:32:49.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:49.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:49.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:49.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Nov 11 16:32:49.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:49.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:49.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:49.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:49.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:49.806: INFO: Nov 11 16:32:51.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:51.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:51.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:51.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Nov 11 16:32:51.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:51.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:51.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:51.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:51.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:51.807: INFO: Nov 11 16:32:53.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:53.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:53.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:53.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Nov 11 16:32:53.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:53.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:53.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:53.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:53.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:53.806: INFO: Nov 11 16:32:55.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:55.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:55.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:55.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Nov 11 16:32:55.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:55.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:55.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:55.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:55.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:55.809: INFO: Nov 11 16:32:57.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:57.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:57.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:57.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Nov 11 16:32:57.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:57.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:57.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:57.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:57.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:57.807: INFO: Nov 11 16:32:59.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:59.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:59.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:32:59.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Nov 11 16:32:59.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:32:59.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:32:59.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:59.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:59.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:32:59.808: INFO: Nov 11 16:33:01.805: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:01.805: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:01.805: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:01.805: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Nov 11 16:33:01.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:01.805: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:01.805: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:01.805: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:01.805: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:01.805: INFO: Nov 11 16:33:03.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:03.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:03.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:03.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Nov 11 16:33:03.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:03.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:03.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:03.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:03.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:03.811: INFO: Nov 11 16:33:05.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:05.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:05.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:05.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Nov 11 16:33:05.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:05.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:05.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:05.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:05.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:05.816: INFO: Nov 11 16:33:07.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:07.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:07.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:07.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Nov 11 16:33:07.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:07.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:07.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:07.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:07.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:07.812: INFO: Nov 11 16:33:09.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:09.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:09.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:09.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Nov 11 16:33:09.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:09.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:09.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:09.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:09.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:09.807: INFO: Nov 11 16:33:11.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:11.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:11.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:11.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Nov 11 16:33:11.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:11.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:11.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:11.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:11.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:11.807: INFO: Nov 11 16:33:13.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:13.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:13.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:13.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Nov 11 16:33:13.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:13.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:13.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:13.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:13.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:13.809: INFO: Nov 11 16:33:15.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:15.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:15.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:15.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Nov 11 16:33:15.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:15.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:15.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:15.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:15.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:15.814: INFO: Nov 11 16:33:17.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:17.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:17.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:17.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Nov 11 16:33:17.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:17.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:17.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:17.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:17.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:17.807: INFO: Nov 11 16:33:19.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:19.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:19.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:19.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Nov 11 16:33:19.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:19.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:19.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:19.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:19.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:19.810: INFO: Nov 11 16:33:21.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:21.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:21.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:21.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Nov 11 16:33:21.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:21.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:21.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:21.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:21.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:21.809: INFO: Nov 11 16:33:23.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:23.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:23.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:23.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Nov 11 16:33:23.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:23.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:23.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:23.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:23.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:23.813: INFO: Nov 11 16:33:25.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:25.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:25.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:25.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Nov 11 16:33:25.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:25.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:25.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:25.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:25.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:25.818: INFO: Nov 11 16:33:27.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:27.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:27.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:27.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Nov 11 16:33:27.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:27.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:27.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:27.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:27.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:27.811: INFO: Nov 11 16:33:29.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:29.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:29.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:29.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Nov 11 16:33:29.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:29.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:29.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:29.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:29.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:29.809: INFO: Nov 11 16:33:31.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:31.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:31.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:31.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Nov 11 16:33:31.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:31.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:31.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:31.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:31.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:31.807: INFO: Nov 11 16:33:33.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:33.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:33.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:33.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Nov 11 16:33:33.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:33.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:33.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:33.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:33.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:33.811: INFO: Nov 11 16:33:35.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:35.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:35.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:35.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Nov 11 16:33:35.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:35.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:35.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:35.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:35.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:35.810: INFO: Nov 11 16:33:37.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:37.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:37.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:37.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Nov 11 16:33:37.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:37.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:37.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:37.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:37.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:37.811: INFO: Nov 11 16:33:39.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:39.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:39.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:39.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Nov 11 16:33:39.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:39.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:39.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:39.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:39.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:39.820: INFO: Nov 11 16:33:41.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:41.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:41.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:41.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Nov 11 16:33:41.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:41.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:41.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:41.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:41.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:41.809: INFO: Nov 11 16:33:43.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:43.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:43.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:43.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Nov 11 16:33:43.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:43.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:43.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:43.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:43.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:43.809: INFO: Nov 11 16:33:45.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:45.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:45.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:45.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Nov 11 16:33:45.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:45.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:45.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:45.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:45.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:45.810: INFO: Nov 11 16:33:47.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:47.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:47.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:47.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Nov 11 16:33:47.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:47.822: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:47.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:47.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:47.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:47.822: INFO: Nov 11 16:33:49.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:49.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:49.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:49.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Nov 11 16:33:49.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:49.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:49.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:49.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:49.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:49.813: INFO: Nov 11 16:33:51.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:51.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:51.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:51.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Nov 11 16:33:51.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:51.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:51.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:51.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:51.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:51.812: INFO: Nov 11 16:33:53.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:53.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:53.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:53.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Nov 11 16:33:53.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:53.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:53.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:53.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:53.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:53.809: INFO: Nov 11 16:33:55.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:55.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:55.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:55.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Nov 11 16:33:55.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:55.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:55.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:55.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:55.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:55.809: INFO: Nov 11 16:33:57.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:57.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:57.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:57.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Nov 11 16:33:57.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:57.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:57.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:57.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:57.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:57.808: INFO: Nov 11 16:33:59.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:59.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:59.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:33:59.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Nov 11 16:33:59.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:33:59.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:33:59.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:59.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:59.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:33:59.815: INFO: Nov 11 16:34:01.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:01.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:01.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:01.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Nov 11 16:34:01.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:01.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:01.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:01.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:01.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:01.808: INFO: Nov 11 16:34:03.997: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:03.997: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:03.997: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:03.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Nov 11 16:34:03.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:03.997: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:03.997: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:03.997: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:03.997: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:03.997: INFO: Nov 11 16:34:05.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:05.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:05.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:05.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Nov 11 16:34:05.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:05.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:05.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:05.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:05.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:05.815: INFO: Nov 11 16:34:07.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:07.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:07.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:07.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Nov 11 16:34:07.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:07.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:07.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:07.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:07.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:07.806: INFO: Nov 11 16:34:09.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:09.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:09.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:09.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Nov 11 16:34:09.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:09.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:09.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:09.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:09.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:09.811: INFO: Nov 11 16:34:11.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:11.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:11.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:11.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Nov 11 16:34:11.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:11.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:11.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:11.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:11.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:11.809: INFO: Nov 11 16:34:13.806: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:13.806: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:13.806: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:13.806: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Nov 11 16:34:13.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:13.806: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:13.806: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:13.806: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:13.806: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:13.806: INFO: Nov 11 16:34:15.852: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:15.852: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:15.853: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:15.853: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Nov 11 16:34:15.853: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:15.853: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:15.853: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:15.853: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:15.853: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:15.853: INFO: Nov 11 16:34:17.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:17.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:17.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:17.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Nov 11 16:34:17.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:17.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:17.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:17.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:17.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:17.808: INFO: Nov 11 16:34:19.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:19.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:19.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:19.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Nov 11 16:34:19.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:19.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:19.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:19.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:19.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:19.816: INFO: Nov 11 16:34:21.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:21.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:21.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:21.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Nov 11 16:34:21.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:21.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:21.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:21.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:21.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:21.811: INFO: Nov 11 16:34:23.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:23.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:23.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:23.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Nov 11 16:34:23.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:23.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:23.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:23.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:23.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:23.807: INFO: Nov 11 16:34:25.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:25.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:25.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:25.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Nov 11 16:34:25.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:25.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:25.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:25.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:25.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:25.816: INFO: Nov 11 16:34:27.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:27.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:27.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:27.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Nov 11 16:34:27.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:27.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:27.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:27.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:27.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:27.808: INFO: Nov 11 16:34:29.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:29.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:29.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:29.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Nov 11 16:34:29.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:29.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:29.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:29.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:29.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:29.807: INFO: Nov 11 16:34:31.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:31.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:31.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:31.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Nov 11 16:34:31.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:31.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:31.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:31.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:31.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:31.807: INFO: Nov 11 16:34:33.804: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:33.804: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:33.804: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:33.804: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Nov 11 16:34:33.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:33.804: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:33.804: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:33.804: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:33.804: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:33.804: INFO: Nov 11 16:34:35.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:35.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:35.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:35.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Nov 11 16:34:35.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:35.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:35.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:35.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:35.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:35.811: INFO: Nov 11 16:34:37.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:37.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:37.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:37.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Nov 11 16:34:37.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:37.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:37.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:37.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:37.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:37.810: INFO: Nov 11 16:34:39.830: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:39.830: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:39.830: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:39.830: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Nov 11 16:34:39.830: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:39.830: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:39.830: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:39.830: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:39.830: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:39.830: INFO: Nov 11 16:34:41.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:41.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:41.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:41.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Nov 11 16:34:41.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:41.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:41.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:41.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:41.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:41.810: INFO: Nov 11 16:34:43.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:43.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:43.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:43.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Nov 11 16:34:43.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:43.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:43.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:43.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:43.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:43.813: INFO: Nov 11 16:34:45.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:45.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:45.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:45.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Nov 11 16:34:45.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:45.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:45.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:45.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:45.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:45.810: INFO: Nov 11 16:34:47.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:47.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:47.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:47.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Nov 11 16:34:47.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:47.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:47.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:47.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:47.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:47.813: INFO: Nov 11 16:34:49.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:49.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:49.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:49.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Nov 11 16:34:49.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:49.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:49.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:49.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:49.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:49.814: INFO: Nov 11 16:34:51.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:51.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:51.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:51.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Nov 11 16:34:51.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:51.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:51.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:51.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:51.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:51.817: INFO: Nov 11 16:34:53.999: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:53.999: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:53.999: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:53.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Nov 11 16:34:53.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:53.999: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:53.999: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:53.999: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:53.999: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:53.999: INFO: Nov 11 16:34:55.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:55.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:55.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:55.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Nov 11 16:34:55.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:55.822: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:55.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:55.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:55.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:55.822: INFO: Nov 11 16:34:57.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:57.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:57.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:57.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Nov 11 16:34:57.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:57.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:57.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:57.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:57.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:57.812: INFO: Nov 11 16:34:59.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:59.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:59.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:34:59.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Nov 11 16:34:59.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:34:59.819: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:34:59.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:59.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:59.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:34:59.819: INFO: Nov 11 16:35:01.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:01.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:01.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:01.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Nov 11 16:35:01.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:01.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:01.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:01.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:01.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:01.812: INFO: Nov 11 16:35:03.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:03.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:03.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:03.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Nov 11 16:35:03.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:03.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:03.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:03.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:03.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:03.812: INFO: Nov 11 16:35:05.826: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:05.826: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:05.826: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:05.826: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Nov 11 16:35:05.826: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:05.826: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:05.826: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:05.826: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:05.826: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:05.826: INFO: Nov 11 16:35:07.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:07.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:07.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:07.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Nov 11 16:35:07.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:07.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:07.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:07.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:07.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:07.813: INFO: Nov 11 16:35:09.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:09.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:09.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:09.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Nov 11 16:35:09.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:09.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:09.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:09.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:09.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:09.813: INFO: Nov 11 16:35:11.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:11.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:11.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:11.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Nov 11 16:35:11.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:11.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:11.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:11.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:11.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:11.811: INFO: Nov 11 16:35:13.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:13.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:13.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:13.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Nov 11 16:35:13.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:13.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:13.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:13.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:13.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:13.815: INFO: Nov 11 16:35:15.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:15.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:15.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:15.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Nov 11 16:35:15.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:15.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:15.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:15.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:15.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:15.820: INFO: Nov 11 16:35:17.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:17.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:17.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:17.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Nov 11 16:35:17.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:17.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:17.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:17.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:17.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:17.809: INFO: Nov 11 16:35:19.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:19.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:19.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:19.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Nov 11 16:35:19.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:19.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:19.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:19.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:19.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:19.812: INFO: Nov 11 16:35:21.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:21.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:21.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:21.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Nov 11 16:35:21.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:21.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:21.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:21.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:21.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:21.817: INFO: Nov 11 16:35:23.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:23.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:23.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:23.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Nov 11 16:35:23.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:23.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:23.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:23.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:23.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:23.810: INFO: Nov 11 16:35:25.831: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:25.831: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:25.831: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:25.831: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Nov 11 16:35:25.831: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:25.831: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:25.831: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:25.831: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:25.831: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:25.831: INFO: Nov 11 16:35:27.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:27.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:27.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:27.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Nov 11 16:35:27.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:27.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:27.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:27.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:27.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:27.815: INFO: Nov 11 16:35:29.824: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:29.824: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:29.824: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:29.824: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Nov 11 16:35:29.824: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:29.824: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:29.824: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:29.824: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:29.824: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:29.824: INFO: Nov 11 16:35:31.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:31.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:31.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:31.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Nov 11 16:35:31.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:31.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:31.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:31.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:31.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:31.816: INFO: Nov 11 16:35:33.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:33.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:33.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:33.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Nov 11 16:35:33.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:33.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:33.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:33.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:33.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:33.820: INFO: Nov 11 16:35:35.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:35.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:35.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:35.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Nov 11 16:35:35.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:35.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:35.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:35.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:35.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:35.813: INFO: Nov 11 16:35:37.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:37.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:37.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:37.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Nov 11 16:35:37.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:37.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:37.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:37.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:37.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:37.820: INFO: Nov 11 16:35:39.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:39.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:39.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:39.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Nov 11 16:35:39.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:39.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:39.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:39.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:39.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:39.812: INFO: Nov 11 16:35:41.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:41.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:41.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:41.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Nov 11 16:35:41.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:41.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:41.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:41.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:41.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:41.817: INFO: Nov 11 16:35:44.003: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:44.003: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:44.003: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:44.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Nov 11 16:35:44.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:44.003: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:44.003: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:44.003: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:44.003: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:44.003: INFO: Nov 11 16:35:45.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:45.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:45.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:45.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Nov 11 16:35:45.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:45.823: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:45.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:45.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:45.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:45.823: INFO: Nov 11 16:35:47.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:47.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:47.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:47.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Nov 11 16:35:47.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:47.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:47.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:47.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:47.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:47.814: INFO: Nov 11 16:35:49.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:49.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:49.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:49.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Nov 11 16:35:49.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:49.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:49.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:49.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:49.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:49.815: INFO: Nov 11 16:35:51.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:51.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:51.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:51.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Nov 11 16:35:51.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:51.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:51.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:51.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:51.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:51.818: INFO: Nov 11 16:35:53.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:53.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:53.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:53.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Nov 11 16:35:53.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:53.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:53.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:53.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:53.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:53.813: INFO: Nov 11 16:35:55.826: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:55.826: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:55.826: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:55.826: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Nov 11 16:35:55.826: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:55.826: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:55.826: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:55.826: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:55.826: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:55.826: INFO: Nov 11 16:35:57.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:57.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:57.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:57.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Nov 11 16:35:57.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:57.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:57.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:57.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:57.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:57.820: INFO: Nov 11 16:35:59.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:59.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:59.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:35:59.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Nov 11 16:35:59.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:35:59.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:35:59.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:59.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:59.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:35:59.815: INFO: Nov 11 16:36:01.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:01.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:01.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:01.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Nov 11 16:36:01.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:01.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:01.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:01.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:01.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:01.811: INFO: Nov 11 16:36:03.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:03.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:03.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:03.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Nov 11 16:36:03.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:03.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:03.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:03.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:03.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:03.814: INFO: Nov 11 16:36:05.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:05.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:05.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:05.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Nov 11 16:36:05.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:05.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:05.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:05.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:05.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:05.820: INFO: Nov 11 16:36:07.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:07.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:07.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:07.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Nov 11 16:36:07.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:07.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:07.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:07.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:07.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:07.813: INFO: Nov 11 16:36:09.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:09.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:09.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:09.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Nov 11 16:36:09.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:09.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:09.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:09.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:09.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:09.816: INFO: Nov 11 16:36:11.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:11.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:11.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:11.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Nov 11 16:36:11.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:11.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:11.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:11.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:11.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:11.817: INFO: Nov 11 16:36:13.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:13.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:13.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:13.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Nov 11 16:36:13.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:13.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:13.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:13.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:13.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:13.817: INFO: Nov 11 16:36:15.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:15.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:15.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:15.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Nov 11 16:36:15.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:15.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:15.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:15.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:15.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:15.812: INFO: Nov 11 16:36:17.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:17.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:17.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:17.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Nov 11 16:36:17.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:17.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:17.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:17.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:17.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:17.817: INFO: Nov 11 16:36:19.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:19.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:19.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:19.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Nov 11 16:36:19.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:19.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:19.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:19.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:19.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:19.808: INFO: Nov 11 16:36:21.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:21.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:21.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:21.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Nov 11 16:36:21.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:21.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:21.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:21.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:21.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:21.809: INFO: Nov 11 16:36:23.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:23.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:23.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:23.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Nov 11 16:36:23.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:23.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:23.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:23.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:23.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:23.810: INFO: Nov 11 16:36:25.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:25.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:25.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:25.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Nov 11 16:36:25.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:25.825: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:25.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:25.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:25.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:25.825: INFO: Nov 11 16:36:27.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:27.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:27.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:27.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Nov 11 16:36:27.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:27.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:27.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:27.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:27.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:27.812: INFO: Nov 11 16:36:29.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:29.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:29.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:29.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Nov 11 16:36:29.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:29.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:29.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:29.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:29.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:29.815: INFO: Nov 11 16:36:31.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:31.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:31.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:31.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Nov 11 16:36:31.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:31.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:31.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:31.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:31.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:31.809: INFO: Nov 11 16:36:33.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:33.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:33.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:33.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Nov 11 16:36:33.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:33.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:33.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:33.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:33.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:33.813: INFO: Nov 11 16:36:36.017: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:36.017: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:36.017: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:36.017: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (361 seconds elapsed) Nov 11 16:36:36.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:36.017: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:36.017: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:36.017: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:36.017: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:36.017: INFO: Nov 11 16:36:37.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:37.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:37.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:37.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Nov 11 16:36:37.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:37.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:37.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:37.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:37.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:37.812: INFO: Nov 11 16:36:39.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:39.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:39.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:39.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Nov 11 16:36:39.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:39.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:39.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:39.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:39.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:39.813: INFO: Nov 11 16:36:41.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:41.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:41.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:41.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Nov 11 16:36:41.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:41.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:41.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:41.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:41.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:41.812: INFO: Nov 11 16:36:43.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:43.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:43.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:43.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Nov 11 16:36:43.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:43.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:43.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:43.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:43.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:43.810: INFO: Nov 11 16:36:45.838: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:45.838: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:45.838: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:45.838: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Nov 11 16:36:45.838: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:45.838: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:45.838: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:45.838: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:45.838: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:45.838: INFO: Nov 11 16:36:47.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:47.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:47.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:47.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Nov 11 16:36:47.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:47.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:47.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:47.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:47.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:47.811: INFO: Nov 11 16:36:49.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:49.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:49.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:49.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Nov 11 16:36:49.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:49.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:49.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:49.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:49.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:49.814: INFO: Nov 11 16:36:51.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:51.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:51.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:51.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Nov 11 16:36:51.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:51.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:51.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:51.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:51.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:51.812: INFO: Nov 11 16:36:53.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:53.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:53.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:53.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Nov 11 16:36:53.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:53.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:53.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:53.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:53.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:53.815: INFO: Nov 11 16:36:55.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:55.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:55.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:55.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Nov 11 16:36:55.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:55.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:55.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:55.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:55.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:55.820: INFO: Nov 11 16:36:57.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:57.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:57.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:36:57.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Nov 11 16:36:57.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:36:57.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:36:57.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:57.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:57.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:36:57.809: INFO: Nov 11 16:37:00.003: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:00.003: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:00.003: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:00.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Nov 11 16:37:00.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:00.003: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:00.003: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:00.003: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:00.003: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:00.003: INFO: Nov 11 16:37:01.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:01.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:01.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:01.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Nov 11 16:37:01.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:01.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:01.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:01.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:01.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:01.814: INFO: Nov 11 16:37:03.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:03.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:03.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:03.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Nov 11 16:37:03.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:03.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:03.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:03.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:03.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:03.809: INFO: Nov 11 16:37:05.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:05.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:05.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:05.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Nov 11 16:37:05.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:05.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:05.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:05.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:05.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:05.810: INFO: Nov 11 16:37:07.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:07.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:07.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:07.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Nov 11 16:37:07.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:07.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:07.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:07.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:07.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:07.811: INFO: Nov 11 16:37:09.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:09.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:09.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:09.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Nov 11 16:37:09.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:09.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:09.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:09.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:09.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:09.810: INFO: Nov 11 16:37:11.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:11.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:11.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:11.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Nov 11 16:37:11.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:11.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:11.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:11.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:11.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:11.811: INFO: Nov 11 16:37:13.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:13.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:13.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:13.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Nov 11 16:37:13.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:13.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:13.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:13.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:13.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:13.820: INFO: Nov 11 16:37:15.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:15.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:15.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:15.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Nov 11 16:37:15.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:15.822: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:15.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:15.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:15.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:15.822: INFO: Nov 11 16:37:17.807: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:17.807: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:17.807: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:17.807: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Nov 11 16:37:17.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:17.807: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:17.807: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:17.807: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:17.807: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:17.807: INFO: Nov 11 16:37:19.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:19.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:19.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:19.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Nov 11 16:37:19.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:19.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:19.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:19.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:19.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:19.817: INFO: Nov 11 16:37:21.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:21.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:21.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:21.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Nov 11 16:37:21.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:21.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:21.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:21.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:21.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:21.814: INFO: Nov 11 16:37:23.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:23.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:23.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:23.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Nov 11 16:37:23.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:23.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:23.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:23.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:23.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:23.810: INFO: Nov 11 16:37:25.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:25.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:25.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:25.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Nov 11 16:37:25.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:25.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:25.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:25.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:25.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:25.815: INFO: Nov 11 16:37:27.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:27.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:27.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:27.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Nov 11 16:37:27.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:27.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:27.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:27.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:27.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:27.809: INFO: Nov 11 16:37:29.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:29.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:29.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:29.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Nov 11 16:37:29.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:29.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:29.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:29.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:29.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:29.812: INFO: Nov 11 16:37:31.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:31.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:31.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:31.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Nov 11 16:37:31.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:31.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:31.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:31.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:31.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:31.811: INFO: Nov 11 16:37:33.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:33.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:33.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:33.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Nov 11 16:37:33.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:33.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:33.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:33.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:33.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:33.814: INFO: Nov 11 16:37:35.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:35.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:35.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:35.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Nov 11 16:37:35.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:35.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:35.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:35.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:35.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:35.818: INFO: Nov 11 16:37:37.829: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:37.829: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:37.829: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:37.829: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Nov 11 16:37:37.829: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:37.829: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:37.829: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:37.829: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:37.829: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:37.829: INFO: Nov 11 16:37:39.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:39.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:39.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:39.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Nov 11 16:37:39.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:39.819: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:39.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:39.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:39.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:39.819: INFO: Nov 11 16:37:41.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:41.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:41.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:41.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Nov 11 16:37:41.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:41.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:41.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:41.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:41.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:41.815: INFO: Nov 11 16:37:43.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:43.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:43.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:43.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Nov 11 16:37:43.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:43.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:43.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:43.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:43.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:43.815: INFO: Nov 11 16:37:45.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:45.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:45.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:45.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Nov 11 16:37:45.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:45.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:45.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:45.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:45.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:45.815: INFO: Nov 11 16:37:47.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:47.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:47.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:47.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Nov 11 16:37:47.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:47.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:47.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:47.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:47.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:47.817: INFO: Nov 11 16:37:49.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:49.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:49.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:49.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Nov 11 16:37:49.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:49.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:49.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:49.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:49.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:49.815: INFO: Nov 11 16:37:51.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:51.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:51.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:51.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Nov 11 16:37:51.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:51.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:51.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:51.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:51.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:51.817: INFO: Nov 11 16:37:53.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:53.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:53.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:53.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Nov 11 16:37:53.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:53.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:53.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:53.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:53.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:53.813: INFO: Nov 11 16:37:55.828: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:55.828: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:55.828: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:55.828: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Nov 11 16:37:55.828: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:55.828: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:55.828: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:55.828: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:55.828: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:55.828: INFO: Nov 11 16:37:57.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:57.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:57.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:57.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Nov 11 16:37:57.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:57.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:57.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:57.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:57.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:57.814: INFO: Nov 11 16:37:59.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:59.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:59.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:37:59.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Nov 11 16:37:59.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:37:59.822: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:37:59.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:59.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:59.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:37:59.822: INFO: Nov 11 16:38:01.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:01.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:01.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:01.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Nov 11 16:38:01.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:01.822: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:01.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:01.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:01.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:01.822: INFO: Nov 11 16:38:03.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:03.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:03.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:03.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Nov 11 16:38:03.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:03.825: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:03.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:03.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:03.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:03.825: INFO: Nov 11 16:38:05.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:05.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:05.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:05.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Nov 11 16:38:05.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:05.823: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:05.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:05.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:05.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:05.823: INFO: Nov 11 16:38:07.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:07.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:07.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:07.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Nov 11 16:38:07.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:07.819: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:07.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:07.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:07.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:07.819: INFO: Nov 11 16:38:10.008: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:10.008: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:10.008: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:10.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Nov 11 16:38:10.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:10.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:10.008: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:10.008: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:10.008: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:10.008: INFO: Nov 11 16:38:11.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:11.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:11.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:11.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Nov 11 16:38:11.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:11.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:11.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:11.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:11.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:11.818: INFO: Nov 11 16:38:13.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:13.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:13.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:13.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Nov 11 16:38:13.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:13.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:13.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:13.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:13.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:13.817: INFO: Nov 11 16:38:15.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:15.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:15.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:15.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Nov 11 16:38:15.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:15.823: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:15.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:15.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:15.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:15.823: INFO: Nov 11 16:38:17.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:17.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:17.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:17.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Nov 11 16:38:17.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:17.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:17.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:17.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:17.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:17.813: INFO: Nov 11 16:38:19.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:19.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:19.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:19.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Nov 11 16:38:19.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:19.825: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:19.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:19.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:19.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:19.825: INFO: Nov 11 16:38:21.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:21.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:21.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:21.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Nov 11 16:38:21.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:21.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:21.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:21.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:21.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:21.820: INFO: Nov 11 16:38:23.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:23.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:23.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:23.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Nov 11 16:38:23.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:23.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:23.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:23.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:23.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:23.816: INFO: Nov 11 16:38:25.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:25.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:25.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:25.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Nov 11 16:38:25.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:25.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:25.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:25.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:25.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:25.811: INFO: Nov 11 16:38:27.825: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:27.825: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:27.825: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:27.825: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Nov 11 16:38:27.825: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:27.825: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:27.825: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:27.825: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:27.825: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:27.825: INFO: Nov 11 16:38:29.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:29.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:29.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:29.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Nov 11 16:38:29.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:29.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:29.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:29.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:29.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:29.812: INFO: Nov 11 16:38:31.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:31.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:31.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:31.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Nov 11 16:38:31.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:31.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:31.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:31.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:31.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:31.815: INFO: Nov 11 16:38:33.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:33.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:33.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:33.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Nov 11 16:38:33.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:33.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:33.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:33.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:33.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:33.810: INFO: Nov 11 16:38:35.822: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:35.822: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:35.822: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:35.822: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Nov 11 16:38:35.822: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:35.822: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:35.822: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:35.822: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:35.822: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:35.822: INFO: Nov 11 16:38:37.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:37.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:37.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:37.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Nov 11 16:38:37.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:37.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:37.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:37.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:37.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:37.813: INFO: Nov 11 16:38:39.821: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:39.821: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:39.821: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:39.821: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Nov 11 16:38:39.821: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:39.821: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:39.821: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:39.821: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:39.821: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:39.821: INFO: Nov 11 16:38:42.001: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:42.001: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:42.001: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:42.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Nov 11 16:38:42.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:42.002: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:42.002: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:42.002: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:42.002: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:42.002: INFO: Nov 11 16:38:43.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:43.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:43.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:43.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Nov 11 16:38:43.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:43.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:43.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:43.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:43.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:43.814: INFO: Nov 11 16:38:45.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:45.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:45.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:45.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Nov 11 16:38:45.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:45.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:45.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:45.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:45.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:45.817: INFO: Nov 11 16:38:47.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:47.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:47.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:47.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Nov 11 16:38:47.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:47.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:47.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:47.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:47.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:47.816: INFO: Nov 11 16:38:49.817: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:49.817: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:49.817: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:49.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Nov 11 16:38:49.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:49.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:49.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:49.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:49.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:49.817: INFO: Nov 11 16:38:51.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:51.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:51.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:51.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Nov 11 16:38:51.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:51.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:51.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:51.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:51.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:51.815: INFO: Nov 11 16:38:53.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:53.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:53.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:53.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Nov 11 16:38:53.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:53.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:53.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:53.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:53.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:53.813: INFO: Nov 11 16:38:55.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:55.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:55.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:55.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Nov 11 16:38:55.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:55.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:55.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:55.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:55.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:55.810: INFO: Nov 11 16:38:57.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:57.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:57.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:57.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Nov 11 16:38:57.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:57.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:57.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:57.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:57.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:57.816: INFO: Nov 11 16:38:59.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:59.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:59.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:38:59.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Nov 11 16:38:59.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:38:59.819: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:38:59.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:59.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:59.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:38:59.819: INFO: Nov 11 16:39:01.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:01.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:01.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:01.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Nov 11 16:39:01.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:01.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:01.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:01.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:01.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:01.810: INFO: Nov 11 16:39:03.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:03.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:03.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:03.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Nov 11 16:39:03.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:03.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:03.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:03.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:03.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:03.813: INFO: Nov 11 16:39:05.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:05.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:05.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:05.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Nov 11 16:39:05.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:05.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:05.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:05.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:05.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:05.814: INFO: Nov 11 16:39:07.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:07.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:07.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:07.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Nov 11 16:39:07.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:07.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:07.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:07.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:07.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:07.809: INFO: Nov 11 16:39:09.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:09.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:09.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:09.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Nov 11 16:39:09.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:09.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:09.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:09.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:09.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:09.809: INFO: Nov 11 16:39:11.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:11.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:11.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:11.817: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Nov 11 16:39:11.817: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:11.817: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:11.817: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:11.817: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:11.817: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:11.817: INFO: Nov 11 16:39:13.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:13.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:13.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:13.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Nov 11 16:39:13.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:13.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:13.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:13.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:13.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:13.811: INFO: Nov 11 16:39:15.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:15.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:15.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:15.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Nov 11 16:39:15.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:15.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:15.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:15.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:15.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:15.813: INFO: Nov 11 16:39:17.813: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:17.813: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:17.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:17.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Nov 11 16:39:17.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:17.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:17.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:17.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:17.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:17.813: INFO: Nov 11 16:39:19.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:19.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:19.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:19.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Nov 11 16:39:19.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:19.823: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:19.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:19.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:19.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:19.823: INFO: Nov 11 16:39:21.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:21.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:21.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:21.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Nov 11 16:39:21.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:21.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:21.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:21.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:21.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:21.812: INFO: Nov 11 16:39:23.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:23.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:23.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:23.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Nov 11 16:39:23.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:23.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:23.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:23.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:23.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:23.808: INFO: Nov 11 16:39:25.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:25.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:25.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:25.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Nov 11 16:39:25.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:25.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:25.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:25.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:25.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:25.812: INFO: Nov 11 16:39:27.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:27.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:27.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:27.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Nov 11 16:39:27.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:27.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:27.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:27.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:27.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:27.811: INFO: Nov 11 16:39:29.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:29.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:29.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:29.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Nov 11 16:39:29.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:29.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:29.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:29.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:29.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:29.809: INFO: Nov 11 16:39:31.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:31.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:31.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:31.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Nov 11 16:39:31.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:31.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:31.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:31.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:31.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:31.812: INFO: Nov 11 16:39:33.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:33.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:33.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:33.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Nov 11 16:39:33.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:33.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:33.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:33.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:33.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:33.811: INFO: Nov 11 16:39:35.820: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:35.820: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:35.820: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:35.820: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Nov 11 16:39:35.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:35.820: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:35.820: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:35.820: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:35.820: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:35.820: INFO: Nov 11 16:39:37.823: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:37.823: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:37.823: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:37.823: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Nov 11 16:39:37.823: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:37.823: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:37.823: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:37.823: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:37.823: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:37.823: INFO: Nov 11 16:39:40.001: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:40.001: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:40.001: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:40.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Nov 11 16:39:40.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:40.001: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:40.001: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:40.001: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:40.001: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:40.001: INFO: Nov 11 16:39:41.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:41.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:41.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:41.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Nov 11 16:39:41.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:41.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:41.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:41.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:41.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:41.811: INFO: Nov 11 16:39:43.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:43.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:43.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:43.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Nov 11 16:39:43.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:43.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:43.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:43.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:43.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:43.811: INFO: Nov 11 16:39:45.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:45.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:45.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:45.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Nov 11 16:39:45.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:45.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:45.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:45.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:45.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:45.814: INFO: Nov 11 16:39:47.809: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:47.809: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:47.809: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:47.809: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Nov 11 16:39:47.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:47.809: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:47.809: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:47.809: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:47.809: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:47.809: INFO: Nov 11 16:39:49.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:49.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:49.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:49.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Nov 11 16:39:49.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:49.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:49.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:49.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:49.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:49.812: INFO: Nov 11 16:39:51.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:51.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:51.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:51.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Nov 11 16:39:51.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:51.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:51.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:51.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:51.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:51.810: INFO: Nov 11 16:39:53.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:53.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:53.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:53.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Nov 11 16:39:53.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:53.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:53.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:53.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:53.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:53.814: INFO: Nov 11 16:39:55.819: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:55.819: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:55.819: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:55.819: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Nov 11 16:39:55.819: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:55.819: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:55.819: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:55.819: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:55.819: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:55.819: INFO: Nov 11 16:39:57.810: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:57.810: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:57.810: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:57.810: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Nov 11 16:39:57.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:57.810: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:57.810: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:57.810: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:57.810: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:57.810: INFO: Nov 11 16:39:59.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:59.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:59.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:39:59.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Nov 11 16:39:59.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:39:59.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:39:59.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:59.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:59.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:39:59.816: INFO: Nov 11 16:40:01.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:01.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:01.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:01.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Nov 11 16:40:01.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:01.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:01.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:01.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:01.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:01.811: INFO: Nov 11 16:40:03.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:03.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:03.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:03.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Nov 11 16:40:03.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:03.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:03.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:03.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:03.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:03.811: INFO: Nov 11 16:40:05.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:05.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:05.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:05.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Nov 11 16:40:05.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:05.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:05.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:05.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:05.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:05.818: INFO: Nov 11 16:40:07.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:07.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:07.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:07.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Nov 11 16:40:07.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:07.812: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:07.812: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:07.812: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:07.812: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:07.812: INFO: Nov 11 16:40:09.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:09.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:09.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:09.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Nov 11 16:40:09.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:09.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:09.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:09.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:09.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:09.811: INFO: Nov 11 16:40:11.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:11.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:11.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:11.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Nov 11 16:40:11.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:11.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:11.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:11.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:11.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:11.814: INFO: Nov 11 16:40:13.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:13.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:13.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:13.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Nov 11 16:40:13.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:13.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:13.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:13.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:13.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:13.811: INFO: Nov 11 16:40:15.818: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:15.818: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:15.818: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:15.818: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Nov 11 16:40:15.818: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:15.818: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:15.818: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:15.818: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:15.818: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:15.818: INFO: Nov 11 16:40:17.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:17.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:17.813: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:17.813: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Nov 11 16:40:17.813: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:17.813: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:17.813: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:17.813: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:17.813: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:17.813: INFO: Nov 11 16:40:19.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:19.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:19.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:19.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Nov 11 16:40:19.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:19.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:19.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:19.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:19.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:19.811: INFO: Nov 11 16:40:21.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:21.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:21.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:21.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Nov 11 16:40:21.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:21.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:21.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:21.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:21.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:21.815: INFO: Nov 11 16:40:23.808: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:23.808: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:23.808: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:23.808: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Nov 11 16:40:23.808: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:23.808: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:23.808: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:23.808: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:23.808: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:23.808: INFO: Nov 11 16:40:25.815: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:25.815: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:25.815: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:25.815: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Nov 11 16:40:25.815: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:25.815: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:25.815: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:25.815: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:25.815: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:25.815: INFO: Nov 11 16:40:27.814: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:27.814: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:27.814: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:27.814: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Nov 11 16:40:27.814: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:27.814: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:27.814: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:27.814: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:27.814: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:27.814: INFO: Nov 11 16:40:29.811: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:29.811: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:29.811: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:29.811: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Nov 11 16:40:29.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:29.811: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:29.811: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:29.811: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:29.811: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:29.811: INFO: Nov 11 16:40:31.816: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:31.816: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:31.816: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:31.816: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Nov 11 16:40:31.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 11 16:40:31.816: INFO: POD NODE PHASE GRACE CONDITIONS Nov 11 16:40:31.816: INFO: kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:31.816: INFO: kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:31.816: INFO: kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv capz-conf-whcdvl-control-plane-2s6hv Pending [] Nov 11 16:40:31.816: INFO: Nov 11 16:40:33.812: INFO: The status of Pod kube-apiserver-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:33.812: INFO: The status of Pod kube-controller-manager-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:33.812: INFO: The status of Pod kube-scheduler-capz-conf-whcdvl-control-plane-2s6hv is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 11 16:40:33.812: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Nov 11 16:40:33.812: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are R