Recent runs || View in Spyglass
PR | pohly: e2e: ginkgo timeouts: preparations |
Result | SUCCESS |
Tests | 4 failed / 6 succeeded |
Started | |
Elapsed | 1h3m |
Revision | c878ded56cb763e4b720b0ca9f1aacc8264431cf |
Refs |
113884 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:249 k8s.io/kubernetes/test/e2e.setupSuite() test/e2e/e2e.go:249 +0x4de k8s.io/kubernetes/test/e2e.glob..func1() test/e2e/e2e.go:81 +0x8f reflect.Value.call({0x669fa40?, 0x788a190?, 0x13?}, {0x75ac456, 0x4}, {0xc00088ff20, 0x0, 0x0?}) /usr/local/go/src/reflect/value.go:584 +0x8c5 reflect.Value.Call({0x669fa40?, 0x788a190?, 0x26cb5ed?}, {0xc000420720?, 0x2659b67?, 0xc000420720?}) /usr/local/go/src/reflect/value.go:368 +0xbcfrom junit.kubetest.01.xml
[SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:77 Nov 14 10:46:33.514: INFO: >>> kubeConfig: /tmp/kubeconfig Nov 14 10:46:33.515: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Nov 14 10:46:33.733: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Nov 14 10:46:33.872: INFO: The status of Pod calico-node-windows-q6n7j is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:33.872: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:33.872: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:33.872: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:33.872: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Nov 14 10:46:33.872: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:33.872: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:33.872: INFO: calico-node-windows-q6n7j capz-conf-8wgrz Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:18 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC ContainersNotReady containers with unready status: [calico-node-startup calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC ContainersNotReady containers with unready status: [calico-node-startup calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:46:33.872: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:33.872: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:33.872: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:33.872: INFO: Nov 14 10:46:36.006: INFO: The status of Pod calico-node-windows-q6n7j is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:36.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:36.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:36.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:36.006: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Nov 14 10:46:36.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:36.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:36.006: INFO: calico-node-windows-q6n7j capz-conf-8wgrz Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:18 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC ContainersNotReady containers with unready status: [calico-node-startup calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC ContainersNotReady containers with unready status: [calico-node-startup calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:46:36.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:36.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:36.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:36.006: INFO: Nov 14 10:46:38.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:38.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:38.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:38.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Nov 14 10:46:38.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:38.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:38.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:38.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:38.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:38.006: INFO: Nov 14 10:46:40.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:40.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:40.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:40.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Nov 14 10:46:40.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:40.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:40.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:40.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:40.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:40.006: INFO: Nov 14 10:46:42.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:42.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:42.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:42.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Nov 14 10:46:42.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:42.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:42.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:42.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:42.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:42.006: INFO: Nov 14 10:46:44.004: INFO: The status of Pod calico-node-windows-z9p5p is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:44.004: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:44.004: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:44.004: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:44.004: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Nov 14 10:46:44.004: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:44.004: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:44.004: INFO: calico-node-windows-z9p5p capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:02 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC }] Nov 14 10:46:44.004: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:44.004: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:44.004: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:44.004: INFO: Nov 14 10:46:46.006: INFO: The status of Pod calico-node-windows-z9p5p is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:46.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:46.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:46.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:46.006: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Nov 14 10:46:46.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:46.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:46.006: INFO: calico-node-windows-z9p5p capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:02 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC }] Nov 14 10:46:46.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:46.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:46.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:46.006: INFO: Nov 14 10:46:48.006: INFO: The status of Pod calico-node-windows-z9p5p is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:48.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:48.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:48.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:48.006: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Nov 14 10:46:48.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:48.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:48.006: INFO: calico-node-windows-z9p5p capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:02 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:43 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC }] Nov 14 10:46:48.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:48.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:48.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:48.006: INFO: Nov 14 10:46:50.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:50.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:50.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:50.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Nov 14 10:46:50.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:50.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:50.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:50.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:50.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:50.013: INFO: Nov 14 10:46:52.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:52.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:52.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:52.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Nov 14 10:46:52.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:52.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:52.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:52.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:52.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:52.006: INFO: Nov 14 10:46:54.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:54.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:54.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:54.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Nov 14 10:46:54.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:54.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:54.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:54.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:54.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:54.005: INFO: Nov 14 10:46:56.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:56.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:56.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:56.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Nov 14 10:46:56.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:56.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:56.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:56.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:56.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:56.009: INFO: Nov 14 10:46:58.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:58.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:58.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:46:58.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Nov 14 10:46:58.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:46:58.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:46:58.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:46:58.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:58.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:46:58.005: INFO: Nov 14 10:47:00.006: INFO: The status of Pod calico-node-windows-q6n7j is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:00.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:00.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:00.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:00.006: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Nov 14 10:47:00.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:00.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:00.006: INFO: calico-node-windows-q6n7j capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:18 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:47:00.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:00.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:00.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:00.006: INFO: Nov 14 10:47:02.010: INFO: The status of Pod calico-node-windows-q6n7j is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:02.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:02.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:02.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:02.010: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Nov 14 10:47:02.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:02.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:02.010: INFO: calico-node-windows-q6n7j capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:18 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:47:02.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:02.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:02.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:02.010: INFO: Nov 14 10:47:04.008: INFO: The status of Pod calico-node-windows-q6n7j is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:04.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:04.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:04.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:04.008: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Nov 14 10:47:04.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:04.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:04.008: INFO: calico-node-windows-q6n7j capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:18 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:47:04.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:04.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:04.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:04.008: INFO: Nov 14 10:47:06.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:06.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:06.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:06.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Nov 14 10:47:06.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:06.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:06.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:06.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:06.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:06.008: INFO: Nov 14 10:47:08.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:08.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:08.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:08.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Nov 14 10:47:08.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:08.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:08.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:08.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:08.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:08.007: INFO: Nov 14 10:47:10.016: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:10.016: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:10.016: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:10.016: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Nov 14 10:47:10.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:10.016: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:10.016: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:10.016: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:10.016: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:10.016: INFO: Nov 14 10:47:12.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:12.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:12.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:12.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Nov 14 10:47:12.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:12.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:12.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:12.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:12.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:12.008: INFO: Nov 14 10:47:14.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:14.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:14.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:14.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Nov 14 10:47:14.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:14.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:14.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:14.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:14.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:14.010: INFO: Nov 14 10:47:16.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:16.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:16.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:16.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Nov 14 10:47:16.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:16.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:16.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:16.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:16.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:16.009: INFO: Nov 14 10:47:18.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:18.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:18.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:18.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Nov 14 10:47:18.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:18.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:18.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:18.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:18.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:18.008: INFO: Nov 14 10:47:20.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:20.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:20.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:20.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Nov 14 10:47:20.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:20.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:20.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:20.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:20.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:20.011: INFO: Nov 14 10:47:22.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:22.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:22.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:22.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Nov 14 10:47:22.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:22.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:22.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:22.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:22.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:22.008: INFO: Nov 14 10:47:24.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:24.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:24.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:24.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Nov 14 10:47:24.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:24.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:24.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:24.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:24.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:24.007: INFO: Nov 14 10:47:26.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:26.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:26.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:26.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Nov 14 10:47:26.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:26.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:26.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:26.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:26.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:26.012: INFO: Nov 14 10:47:28.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:28.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:28.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:28.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Nov 14 10:47:28.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:28.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:28.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:28.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:28.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:28.007: INFO: Nov 14 10:47:30.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:30.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:30.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:30.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Nov 14 10:47:30.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:30.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:30.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:30.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:30.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:30.006: INFO: Nov 14 10:47:32.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:32.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:32.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:32.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Nov 14 10:47:32.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:32.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:32.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:32.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:32.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:32.008: INFO: Nov 14 10:47:34.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:34.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:34.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:34.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Nov 14 10:47:34.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:34.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:34.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:34.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:34.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:34.007: INFO: Nov 14 10:47:36.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:36.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:36.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:36.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Nov 14 10:47:36.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:36.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:36.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:36.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:36.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:36.006: INFO: Nov 14 10:47:38.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:38.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:38.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:38.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Nov 14 10:47:38.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:38.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:38.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:38.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:38.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:38.005: INFO: Nov 14 10:47:40.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:40.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:40.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:40.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Nov 14 10:47:40.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:40.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:40.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:40.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:40.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:40.007: INFO: Nov 14 10:47:42.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:42.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:42.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:42.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Nov 14 10:47:42.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:42.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:42.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:42.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:42.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:42.007: INFO: Nov 14 10:47:44.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:44.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:44.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:44.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Nov 14 10:47:44.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:44.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:44.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:44.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:44.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:44.008: INFO: Nov 14 10:47:46.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:46.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:46.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:46.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Nov 14 10:47:46.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:46.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:46.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:46.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:46.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:46.010: INFO: Nov 14 10:47:48.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:48.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:48.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:48.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Nov 14 10:47:48.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:48.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:48.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:48.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:48.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:48.008: INFO: Nov 14 10:47:50.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:50.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:50.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:50.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Nov 14 10:47:50.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:50.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:50.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:50.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:50.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:50.007: INFO: Nov 14 10:47:52.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:52.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:52.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:52.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Nov 14 10:47:52.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:52.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:52.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:52.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:52.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:52.008: INFO: Nov 14 10:47:54.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:54.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:54.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:54.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Nov 14 10:47:54.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:54.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:54.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:54.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:54.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:54.006: INFO: Nov 14 10:47:56.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:56.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:56.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:56.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Nov 14 10:47:56.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:56.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:56.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:56.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:56.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:56.011: INFO: Nov 14 10:47:58.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:58.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:58.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:47:58.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Nov 14 10:47:58.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:47:58.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:47:58.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:47:58.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:58.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:47:58.009: INFO: Nov 14 10:48:00.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:00.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:00.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:00.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Nov 14 10:48:00.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:00.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:00.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:00.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:00.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:00.007: INFO: Nov 14 10:48:02.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:02.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:02.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:02.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Nov 14 10:48:02.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:02.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:02.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:02.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:02.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:02.007: INFO: Nov 14 10:48:04.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:04.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:04.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:04.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Nov 14 10:48:04.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:04.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:04.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:04.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:04.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:04.007: INFO: Nov 14 10:48:06.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:06.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:06.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:06.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Nov 14 10:48:06.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:06.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:06.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:06.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:06.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:06.008: INFO: Nov 14 10:48:08.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:08.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:08.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:08.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Nov 14 10:48:08.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:08.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:08.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:08.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:08.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:08.007: INFO: Nov 14 10:48:10.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:10.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:10.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:10.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Nov 14 10:48:10.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:10.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:10.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:10.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:10.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:10.007: INFO: Nov 14 10:48:12.072: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:12.073: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:12.073: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:12.073: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Nov 14 10:48:12.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:12.073: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:12.073: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:12.073: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:12.073: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:12.073: INFO: Nov 14 10:48:14.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:14.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:14.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:14.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Nov 14 10:48:14.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:14.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:14.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:14.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:14.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:14.010: INFO: Nov 14 10:48:16.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:16.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:16.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:16.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Nov 14 10:48:16.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:16.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:16.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:16.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:16.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:16.007: INFO: Nov 14 10:48:18.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:18.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:18.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:18.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Nov 14 10:48:18.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:18.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:18.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:18.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:18.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:18.006: INFO: Nov 14 10:48:20.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:20.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:20.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:20.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Nov 14 10:48:20.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:20.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:20.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:20.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:20.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:20.007: INFO: Nov 14 10:48:22.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:22.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:22.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:22.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Nov 14 10:48:22.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:22.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:22.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:22.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:22.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:22.006: INFO: Nov 14 10:48:24.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:24.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:24.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:24.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Nov 14 10:48:24.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:24.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:24.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:24.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:24.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:24.013: INFO: Nov 14 10:48:26.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:26.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:26.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:26.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Nov 14 10:48:26.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:26.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:26.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:26.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:26.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:26.005: INFO: Nov 14 10:48:28.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:28.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:28.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:28.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Nov 14 10:48:28.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:28.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:28.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:28.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:28.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:28.007: INFO: Nov 14 10:48:30.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:30.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:30.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:30.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Nov 14 10:48:30.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:30.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:30.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:30.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:30.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:30.008: INFO: Nov 14 10:48:32.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:32.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:32.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:32.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Nov 14 10:48:32.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:32.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:32.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:32.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:32.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:32.005: INFO: Nov 14 10:48:34.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:34.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:34.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:34.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Nov 14 10:48:34.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:34.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:34.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:34.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:34.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:34.005: INFO: Nov 14 10:48:36.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:36.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:36.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:36.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Nov 14 10:48:36.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:36.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:36.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:36.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:36.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:36.006: INFO: Nov 14 10:48:38.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:38.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:38.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:38.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Nov 14 10:48:38.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:38.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:38.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:38.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:38.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:38.006: INFO: Nov 14 10:48:40.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:40.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:40.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:40.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Nov 14 10:48:40.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:40.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:40.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:40.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:40.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:40.006: INFO: Nov 14 10:48:42.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:42.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:42.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:42.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Nov 14 10:48:42.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:42.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:42.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:42.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:42.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:42.005: INFO: Nov 14 10:48:44.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:44.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:44.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:44.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Nov 14 10:48:44.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:44.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:44.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:44.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:44.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:44.006: INFO: Nov 14 10:48:46.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:46.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:46.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:46.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Nov 14 10:48:46.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:46.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:46.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:46.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:46.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:46.005: INFO: Nov 14 10:48:48.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:48.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:48.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:48.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Nov 14 10:48:48.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:48.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:48.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:48.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:48.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:48.007: INFO: Nov 14 10:48:50.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:50.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:50.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:50.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Nov 14 10:48:50.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:50.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:50.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:50.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:50.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:50.007: INFO: Nov 14 10:48:52.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:52.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:52.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:52.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Nov 14 10:48:52.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:52.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:52.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:52.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:52.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:52.006: INFO: Nov 14 10:48:54.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:54.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:54.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:54.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Nov 14 10:48:54.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:54.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:54.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:54.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:54.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:54.007: INFO: Nov 14 10:48:56.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:56.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:56.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:56.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Nov 14 10:48:56.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:56.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:56.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:56.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:56.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:56.009: INFO: Nov 14 10:48:58.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:58.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:58.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:48:58.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Nov 14 10:48:58.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:48:58.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:48:58.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:48:58.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:58.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:48:58.006: INFO: Nov 14 10:49:00.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:00.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:00.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:00.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Nov 14 10:49:00.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:00.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:00.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:00.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:00.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:00.006: INFO: Nov 14 10:49:02.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:02.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:02.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:02.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Nov 14 10:49:02.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:02.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:02.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:02.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:02.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:02.006: INFO: Nov 14 10:49:04.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:04.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:04.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:04.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Nov 14 10:49:04.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:04.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:04.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:04.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:04.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:04.007: INFO: Nov 14 10:49:06.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:06.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:06.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:06.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Nov 14 10:49:06.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:06.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:06.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:06.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:06.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:06.006: INFO: Nov 14 10:49:08.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:08.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:08.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:08.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Nov 14 10:49:08.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:08.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:08.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:08.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:08.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:08.005: INFO: Nov 14 10:49:10.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:10.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:10.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:10.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Nov 14 10:49:10.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:10.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:10.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:10.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:10.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:10.010: INFO: Nov 14 10:49:12.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:12.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:12.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:12.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Nov 14 10:49:12.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:12.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:12.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:12.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:12.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:12.014: INFO: Nov 14 10:49:14.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:14.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:14.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:14.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Nov 14 10:49:14.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:14.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:14.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:14.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:14.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:14.006: INFO: Nov 14 10:49:16.126: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:16.126: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:16.126: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:16.126: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Nov 14 10:49:16.126: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:16.126: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:16.126: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:16.126: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:16.126: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:16.126: INFO: Nov 14 10:49:18.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:18.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:18.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:18.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Nov 14 10:49:18.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:18.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:18.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:18.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:18.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:18.006: INFO: Nov 14 10:49:20.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:20.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:20.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:20.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Nov 14 10:49:20.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:20.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:20.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:20.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:20.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:20.006: INFO: Nov 14 10:49:22.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:22.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:22.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:22.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Nov 14 10:49:22.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:22.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:22.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:22.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:22.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:22.010: INFO: Nov 14 10:49:24.020: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:24.020: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:24.020: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:24.020: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Nov 14 10:49:24.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:24.020: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:24.020: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:24.020: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:24.020: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:24.020: INFO: Nov 14 10:49:26.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:26.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:26.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:26.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Nov 14 10:49:26.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:26.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:26.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:26.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:26.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:26.010: INFO: Nov 14 10:49:28.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:28.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:28.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:28.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Nov 14 10:49:28.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:28.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:28.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:28.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:28.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:28.007: INFO: Nov 14 10:49:30.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:30.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:30.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:30.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Nov 14 10:49:30.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:30.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:30.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:30.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:30.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:30.007: INFO: Nov 14 10:49:32.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:32.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:32.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:32.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Nov 14 10:49:32.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:32.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:32.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:32.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:32.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:32.006: INFO: Nov 14 10:49:34.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:34.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:34.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:34.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Nov 14 10:49:34.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:34.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:34.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:34.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:34.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:34.005: INFO: Nov 14 10:49:36.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:36.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:36.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:36.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Nov 14 10:49:36.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:36.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:36.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:36.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:36.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:36.012: INFO: Nov 14 10:49:38.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:38.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:38.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:38.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Nov 14 10:49:38.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:38.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:38.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:38.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:38.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:38.005: INFO: Nov 14 10:49:40.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:40.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:40.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:40.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Nov 14 10:49:40.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:40.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:40.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:40.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:40.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:40.006: INFO: Nov 14 10:49:42.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:42.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:42.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:42.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Nov 14 10:49:42.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:42.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:42.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:42.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:42.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:42.005: INFO: Nov 14 10:49:44.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:44.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:44.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:44.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Nov 14 10:49:44.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:44.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:44.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:44.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:44.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:44.006: INFO: Nov 14 10:49:46.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:46.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:46.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:46.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Nov 14 10:49:46.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:46.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:46.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:46.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:46.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:46.007: INFO: Nov 14 10:49:48.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:48.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:48.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:48.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Nov 14 10:49:48.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:48.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:48.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:48.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:48.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:48.007: INFO: Nov 14 10:49:50.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:50.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:50.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:50.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Nov 14 10:49:50.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:50.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:50.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:50.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:50.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:50.006: INFO: Nov 14 10:49:52.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:52.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:52.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:52.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Nov 14 10:49:52.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:52.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:52.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:52.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:52.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:52.006: INFO: Nov 14 10:49:54.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:54.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:54.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:54.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Nov 14 10:49:54.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:54.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:54.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:54.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:54.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:54.009: INFO: Nov 14 10:49:56.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:56.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:56.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:56.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Nov 14 10:49:56.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:56.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:56.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:56.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:56.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:56.008: INFO: Nov 14 10:49:58.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:58.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:58.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:49:58.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Nov 14 10:49:58.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:49:58.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:49:58.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:49:58.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:58.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:49:58.005: INFO: Nov 14 10:50:00.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:00.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:00.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:00.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Nov 14 10:50:00.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:00.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:00.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:00.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:00.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:00.005: INFO: Nov 14 10:50:02.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:02.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:02.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:02.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Nov 14 10:50:02.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:02.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:02.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:02.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:02.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:02.009: INFO: Nov 14 10:50:04.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:04.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:04.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:04.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Nov 14 10:50:04.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:04.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:04.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:04.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:04.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:04.005: INFO: Nov 14 10:50:06.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:06.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:06.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:06.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Nov 14 10:50:06.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:06.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:06.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:06.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:06.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:06.005: INFO: Nov 14 10:50:08.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:08.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:08.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:08.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Nov 14 10:50:08.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:08.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:08.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:08.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:08.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:08.007: INFO: Nov 14 10:50:10.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:10.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:10.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:10.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Nov 14 10:50:10.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:10.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:10.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:10.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:10.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:10.009: INFO: Nov 14 10:50:12.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:12.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:12.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:12.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Nov 14 10:50:12.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:12.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:12.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:12.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:12.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:12.007: INFO: Nov 14 10:50:14.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:14.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:14.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:14.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Nov 14 10:50:14.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:14.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:14.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:14.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:14.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:14.008: INFO: Nov 14 10:50:16.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:16.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:16.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:16.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Nov 14 10:50:16.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:16.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:16.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:16.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:16.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:16.006: INFO: Nov 14 10:50:18.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:18.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:18.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:18.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Nov 14 10:50:18.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:18.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:18.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:18.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:18.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:18.005: INFO: Nov 14 10:50:20.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:20.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:20.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:20.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Nov 14 10:50:20.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:20.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:20.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:20.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:20.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:20.009: INFO: Nov 14 10:50:22.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:22.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:22.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:22.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Nov 14 10:50:22.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:22.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:22.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:22.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:22.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:22.006: INFO: Nov 14 10:50:24.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:24.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:24.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:24.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Nov 14 10:50:24.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:24.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:24.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:24.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:24.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:24.005: INFO: Nov 14 10:50:26.018: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:26.018: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:26.018: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:26.018: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Nov 14 10:50:26.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:26.018: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:26.018: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:26.018: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:26.018: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:26.018: INFO: Nov 14 10:50:28.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:28.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:28.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:28.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Nov 14 10:50:28.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:28.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:28.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:28.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:28.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:28.010: INFO: Nov 14 10:50:30.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:30.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:30.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:30.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Nov 14 10:50:30.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:30.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:30.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:30.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:30.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:30.005: INFO: Nov 14 10:50:32.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:32.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:32.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:32.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Nov 14 10:50:32.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:32.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:32.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:32.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:32.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:32.005: INFO: Nov 14 10:50:34.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:34.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:34.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:34.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Nov 14 10:50:34.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:34.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:34.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:34.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:34.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:34.010: INFO: Nov 14 10:50:36.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:36.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:36.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:36.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Nov 14 10:50:36.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:36.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:36.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:36.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:36.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:36.006: INFO: Nov 14 10:50:38.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:38.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:38.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:38.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Nov 14 10:50:38.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:38.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:38.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:38.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:38.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:38.008: INFO: Nov 14 10:50:40.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:40.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:40.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:40.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Nov 14 10:50:40.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:40.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:40.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:40.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:40.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:40.008: INFO: Nov 14 10:50:42.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:42.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:42.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:42.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Nov 14 10:50:42.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:42.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:42.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:42.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:42.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:42.005: INFO: Nov 14 10:50:44.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:44.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:44.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:44.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Nov 14 10:50:44.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:44.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:44.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:44.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:44.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:44.007: INFO: Nov 14 10:50:46.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:46.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:46.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:46.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Nov 14 10:50:46.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:46.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:46.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:46.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:46.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:46.006: INFO: Nov 14 10:50:48.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:48.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:48.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:48.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Nov 14 10:50:48.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:48.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:48.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:48.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:48.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:48.008: INFO: Nov 14 10:50:50.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:50.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:50.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:50.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Nov 14 10:50:50.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:50.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:50.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:50.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:50.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:50.009: INFO: Nov 14 10:50:52.026: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:52.026: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:52.026: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:52.026: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Nov 14 10:50:52.026: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:52.026: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:52.026: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:52.026: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:52.026: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:52.026: INFO: Nov 14 10:50:54.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:54.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:54.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:54.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Nov 14 10:50:54.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:54.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:54.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:54.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:54.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:54.008: INFO: Nov 14 10:50:56.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:56.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:56.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:56.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Nov 14 10:50:56.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:56.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:56.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:56.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:56.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:56.007: INFO: Nov 14 10:50:58.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:58.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:58.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:50:58.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Nov 14 10:50:58.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:50:58.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:50:58.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:50:58.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:58.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:50:58.006: INFO: Nov 14 10:51:00.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:00.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:00.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:00.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Nov 14 10:51:00.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:00.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:00.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:00.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:00.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:00.008: INFO: Nov 14 10:51:02.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:02.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:02.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:02.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Nov 14 10:51:02.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:02.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:02.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:02.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:02.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:02.006: INFO: Nov 14 10:51:04.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:04.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:04.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:04.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Nov 14 10:51:04.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:04.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:04.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:04.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:04.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:04.006: INFO: Nov 14 10:51:06.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:06.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:06.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:06.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Nov 14 10:51:06.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:06.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:06.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:06.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:06.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:06.006: INFO: Nov 14 10:51:08.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:08.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:08.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:08.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Nov 14 10:51:08.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:08.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:08.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:08.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:08.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:08.008: INFO: Nov 14 10:51:10.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:10.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:10.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:10.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Nov 14 10:51:10.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:10.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:10.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:10.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:10.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:10.007: INFO: Nov 14 10:51:12.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:12.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:12.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:12.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Nov 14 10:51:12.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:12.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:12.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:12.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:12.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:12.005: INFO: Nov 14 10:51:14.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:14.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:14.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:14.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Nov 14 10:51:14.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:14.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:14.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:14.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:14.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:14.006: INFO: Nov 14 10:51:16.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:16.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:16.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:16.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Nov 14 10:51:16.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:16.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:16.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:16.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:16.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:16.006: INFO: Nov 14 10:51:18.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:18.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:18.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:18.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Nov 14 10:51:18.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:18.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:18.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:18.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:18.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:18.014: INFO: Nov 14 10:51:20.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:20.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:20.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:20.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Nov 14 10:51:20.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:20.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:20.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:20.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:20.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:20.007: INFO: Nov 14 10:51:22.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:22.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:22.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:22.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Nov 14 10:51:22.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:22.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:22.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:22.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:22.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:22.006: INFO: Nov 14 10:51:24.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:24.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:24.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:24.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Nov 14 10:51:24.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:24.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:24.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:24.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:24.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:24.013: INFO: Nov 14 10:51:26.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:26.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:26.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:26.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Nov 14 10:51:26.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:26.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:26.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:26.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:26.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:26.010: INFO: Nov 14 10:51:28.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:28.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:28.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:28.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Nov 14 10:51:28.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:28.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:28.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:28.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:28.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:28.006: INFO: Nov 14 10:51:30.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:30.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:30.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:30.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Nov 14 10:51:30.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:30.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:30.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:30.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:30.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:30.009: INFO: Nov 14 10:51:32.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:32.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:32.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:32.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Nov 14 10:51:32.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:32.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:32.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:32.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:32.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:32.008: INFO: Nov 14 10:51:34.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:34.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:34.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:34.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Nov 14 10:51:34.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:34.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:34.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:34.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:34.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:34.007: INFO: Nov 14 10:51:36.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:36.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:36.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:36.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Nov 14 10:51:36.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:36.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:36.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:36.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:36.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:36.006: INFO: Nov 14 10:51:38.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:38.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:38.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:38.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Nov 14 10:51:38.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:38.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:38.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:38.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:38.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:38.006: INFO: Nov 14 10:51:40.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:40.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:40.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:40.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Nov 14 10:51:40.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:40.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:40.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:40.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:40.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:40.008: INFO: Nov 14 10:51:42.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:42.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:42.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:42.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Nov 14 10:51:42.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:42.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:42.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:42.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:42.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:42.006: INFO: Nov 14 10:51:44.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:44.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:44.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:44.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Nov 14 10:51:44.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:44.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:44.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:44.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:44.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:44.008: INFO: Nov 14 10:51:46.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:46.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:46.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:46.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Nov 14 10:51:46.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:46.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:46.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:46.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:46.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:46.007: INFO: Nov 14 10:51:48.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:48.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:48.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:48.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Nov 14 10:51:48.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:48.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:48.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:48.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:48.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:48.006: INFO: Nov 14 10:51:50.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:50.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:50.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:50.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Nov 14 10:51:50.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:50.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:50.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:50.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:50.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:50.005: INFO: Nov 14 10:51:52.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:52.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:52.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:52.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Nov 14 10:51:52.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:52.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:52.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:52.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:52.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:52.007: INFO: Nov 14 10:51:54.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:54.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:54.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:54.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Nov 14 10:51:54.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:54.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:54.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:54.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:54.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:54.009: INFO: Nov 14 10:51:56.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:56.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:56.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:56.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Nov 14 10:51:56.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:56.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:56.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:56.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:56.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:56.007: INFO: Nov 14 10:51:58.128: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:58.128: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:58.128: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:51:58.128: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Nov 14 10:51:58.128: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:51:58.128: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:51:58.128: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:51:58.128: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:58.128: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:51:58.128: INFO: Nov 14 10:52:00.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:00.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:00.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:00.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Nov 14 10:52:00.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:00.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:00.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:00.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:00.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:00.007: INFO: Nov 14 10:52:02.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:02.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:02.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:02.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Nov 14 10:52:02.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:02.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:02.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:02.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:02.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:02.006: INFO: Nov 14 10:52:04.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:04.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:04.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:04.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Nov 14 10:52:04.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:04.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:04.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:04.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:04.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:04.006: INFO: Nov 14 10:52:06.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:06.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:06.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:06.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Nov 14 10:52:06.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:06.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:06.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:06.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:06.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:06.006: INFO: Nov 14 10:52:08.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:08.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:08.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:08.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Nov 14 10:52:08.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:08.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:08.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:08.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:08.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:08.006: INFO: Nov 14 10:52:10.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:10.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:10.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:10.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Nov 14 10:52:10.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:10.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:10.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:10.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:10.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:10.008: INFO: Nov 14 10:52:12.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:12.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:12.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:12.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Nov 14 10:52:12.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:12.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:12.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:12.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:12.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:12.007: INFO: Nov 14 10:52:14.006: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:14.006: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:14.006: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:14.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Nov 14 10:52:14.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:14.006: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:14.006: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:14.006: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:14.006: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:14.006: INFO: Nov 14 10:52:16.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:16.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:16.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:16.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Nov 14 10:52:16.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:16.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:16.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:16.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:16.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:16.007: INFO: Nov 14 10:52:18.124: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:18.124: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:18.124: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:18.124: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Nov 14 10:52:18.124: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:18.124: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:18.124: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:18.124: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:18.124: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:18.124: INFO: Nov 14 10:52:20.007: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:20.007: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:20.007: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:20.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Nov 14 10:52:20.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:20.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:20.007: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:20.007: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:20.007: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:20.007: INFO: Nov 14 10:52:22.005: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:22.005: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:22.005: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:22.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Nov 14 10:52:22.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:22.005: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:22.005: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:22.005: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:22.005: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:22.005: INFO: Nov 14 10:52:24.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:24.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:24.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:24.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Nov 14 10:52:24.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:24.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:24.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:24.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:24.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:24.008: INFO: Nov 14 10:52:26.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:26.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:26.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:26.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Nov 14 10:52:26.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:26.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:26.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:26.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:26.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:26.009: INFO: Nov 14 10:52:28.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:28.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:28.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:28.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Nov 14 10:52:28.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:28.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:28.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:28.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:28.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:28.008: INFO: Nov 14 10:52:30.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:30.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:30.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:30.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Nov 14 10:52:30.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:30.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:30.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:30.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:30.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:30.013: INFO: Nov 14 10:52:32.130: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:32.130: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:32.130: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:32.130: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Nov 14 10:52:32.130: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:32.130: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:32.130: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:32.130: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:32.130: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:32.130: INFO: Nov 14 10:52:34.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:34.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:34.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:34.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Nov 14 10:52:34.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:34.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:34.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:34.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:34.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:34.010: INFO: Nov 14 10:52:36.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:36.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:36.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:36.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Nov 14 10:52:36.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:36.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:36.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:36.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:36.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:36.010: INFO: Nov 14 10:52:38.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:38.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:38.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:38.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Nov 14 10:52:38.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:38.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:38.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:38.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:38.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:38.010: INFO: Nov 14 10:52:40.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:40.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:40.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:40.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Nov 14 10:52:40.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:40.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:40.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:40.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:40.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:40.014: INFO: Nov 14 10:52:42.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:42.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:42.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:42.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Nov 14 10:52:42.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:42.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:42.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:42.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:42.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:42.010: INFO: Nov 14 10:52:44.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:44.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:44.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:44.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Nov 14 10:52:44.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:44.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:44.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:44.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:44.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:44.012: INFO: Nov 14 10:52:46.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:46.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:46.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:46.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Nov 14 10:52:46.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:46.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:46.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:46.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:46.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:46.009: INFO: Nov 14 10:52:48.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:48.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:48.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:48.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Nov 14 10:52:48.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:48.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:48.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:48.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:48.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:48.013: INFO: Nov 14 10:52:50.015: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:50.015: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:50.015: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:50.015: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Nov 14 10:52:50.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:50.015: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:50.015: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:50.015: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:50.015: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:50.015: INFO: Nov 14 10:52:52.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:52.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:52.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:52.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Nov 14 10:52:52.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:52.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:52.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:52.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:52.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:52.011: INFO: Nov 14 10:52:54.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:54.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:54.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:54.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Nov 14 10:52:54.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:54.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:54.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:54.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:54.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:54.008: INFO: Nov 14 10:52:56.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:56.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:56.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:56.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Nov 14 10:52:56.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:56.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:56.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:56.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:56.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:56.010: INFO: Nov 14 10:52:58.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:58.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:58.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:52:58.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Nov 14 10:52:58.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:52:58.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:52:58.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:52:58.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:58.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:52:58.010: INFO: Nov 14 10:53:00.018: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:00.018: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:00.018: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:00.018: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Nov 14 10:53:00.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:00.018: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:00.018: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:00.018: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:00.018: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:00.018: INFO: Nov 14 10:53:02.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:02.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:02.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:02.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Nov 14 10:53:02.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:02.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:02.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:02.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:02.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:02.012: INFO: Nov 14 10:53:04.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:04.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:04.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:04.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Nov 14 10:53:04.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:04.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:04.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:04.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:04.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:04.013: INFO: Nov 14 10:53:06.129: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:06.129: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:06.129: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:06.129: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Nov 14 10:53:06.129: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:06.129: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:06.129: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:06.129: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:06.129: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:06.129: INFO: Nov 14 10:53:08.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:08.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:08.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:08.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Nov 14 10:53:08.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:08.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:08.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:08.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:08.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:08.014: INFO: Nov 14 10:53:10.016: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:10.016: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:10.016: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:10.016: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Nov 14 10:53:10.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:10.016: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:10.016: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:10.016: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:10.016: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:10.016: INFO: Nov 14 10:53:12.035: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:12.035: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:12.035: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:12.035: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Nov 14 10:53:12.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:12.035: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:12.035: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:12.036: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:12.036: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:12.036: INFO: Nov 14 10:53:14.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:14.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:14.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:14.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Nov 14 10:53:14.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:14.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:14.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:14.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:14.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:14.009: INFO: Nov 14 10:53:16.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:16.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:16.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:16.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Nov 14 10:53:16.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:16.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:16.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:16.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:16.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:16.012: INFO: Nov 14 10:53:18.015: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:18.015: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:18.015: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:18.015: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Nov 14 10:53:18.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:18.015: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:18.015: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:18.015: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:18.015: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:18.015: INFO: Nov 14 10:53:20.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:20.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:20.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:20.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Nov 14 10:53:20.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:20.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:20.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:20.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:20.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:20.013: INFO: Nov 14 10:53:22.017: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:22.017: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:22.017: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:22.017: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Nov 14 10:53:22.017: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:22.017: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:22.017: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:22.017: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:22.017: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:22.017: INFO: Nov 14 10:53:24.016: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:24.016: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:24.016: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:24.016: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Nov 14 10:53:24.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:24.016: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:24.016: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:24.016: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:24.016: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:24.016: INFO: Nov 14 10:53:26.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:26.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:26.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:26.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Nov 14 10:53:26.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:26.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:26.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:26.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:26.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:26.009: INFO: Nov 14 10:53:28.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:28.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:28.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:28.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Nov 14 10:53:28.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:28.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:28.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:28.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:28.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:28.008: INFO: Nov 14 10:53:30.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:30.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:30.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:30.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Nov 14 10:53:30.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:30.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:30.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:30.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:30.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:30.014: INFO: Nov 14 10:53:32.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:32.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:32.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:32.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Nov 14 10:53:32.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:32.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:32.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:32.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:32.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:32.010: INFO: Nov 14 10:53:34.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:34.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:34.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:34.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Nov 14 10:53:34.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:34.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:34.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:34.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:34.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:34.011: INFO: Nov 14 10:53:36.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:36.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:36.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:36.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Nov 14 10:53:36.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:36.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:36.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:36.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:36.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:36.013: INFO: Nov 14 10:53:38.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:38.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:38.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:38.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Nov 14 10:53:38.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:38.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:38.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:38.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:38.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:38.011: INFO: Nov 14 10:53:40.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:40.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:40.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:40.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Nov 14 10:53:40.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:40.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:40.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:40.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:40.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:40.012: INFO: Nov 14 10:53:42.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:42.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:42.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:42.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Nov 14 10:53:42.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:42.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:42.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:42.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:42.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:42.012: INFO: Nov 14 10:53:44.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:44.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:44.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:44.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Nov 14 10:53:44.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:44.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:44.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:44.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:44.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:44.012: INFO: Nov 14 10:53:46.128: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:46.128: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:46.128: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:46.128: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Nov 14 10:53:46.128: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:46.128: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:46.128: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:46.128: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:46.128: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:46.128: INFO: Nov 14 10:53:48.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:48.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:48.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:48.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Nov 14 10:53:48.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:48.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:48.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:48.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:48.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:48.011: INFO: Nov 14 10:53:50.020: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:50.020: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:50.020: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:50.020: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Nov 14 10:53:50.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:50.020: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:50.020: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:50.020: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:50.020: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:50.020: INFO: Nov 14 10:53:52.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:52.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:52.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:52.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Nov 14 10:53:52.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:52.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:52.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:52.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:52.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:52.011: INFO: Nov 14 10:53:54.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:54.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:54.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:54.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Nov 14 10:53:54.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:54.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:54.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:54.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:54.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:54.011: INFO: Nov 14 10:53:56.015: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:56.015: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:56.015: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:56.015: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Nov 14 10:53:56.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:56.015: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:56.015: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:56.015: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:56.015: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:56.015: INFO: Nov 14 10:53:58.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:58.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:58.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:53:58.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Nov 14 10:53:58.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:53:58.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:53:58.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:53:58.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:58.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:53:58.010: INFO: Nov 14 10:54:00.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:00.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:00.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:00.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Nov 14 10:54:00.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:00.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:00.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:00.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:00.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:00.010: INFO: Nov 14 10:54:02.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:02.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:02.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:02.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Nov 14 10:54:02.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:02.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:02.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:02.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:02.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:02.010: INFO: Nov 14 10:54:04.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:04.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:04.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:04.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Nov 14 10:54:04.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:04.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:04.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:04.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:04.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:04.013: INFO: Nov 14 10:54:06.015: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:06.015: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:06.015: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:06.015: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Nov 14 10:54:06.015: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:06.015: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:06.015: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:06.015: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:06.015: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:06.015: INFO: Nov 14 10:54:08.020: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:08.020: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:08.020: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:08.020: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Nov 14 10:54:08.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:08.020: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:08.020: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:08.020: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:08.020: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:08.020: INFO: Nov 14 10:54:10.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:10.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:10.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:10.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Nov 14 10:54:10.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:10.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:10.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:10.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:10.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:10.011: INFO: Nov 14 10:54:12.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:12.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:12.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:12.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Nov 14 10:54:12.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:12.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:12.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:12.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:12.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:12.011: INFO: Nov 14 10:54:14.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:14.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:14.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:14.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Nov 14 10:54:14.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:14.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:14.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:14.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:14.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:14.011: INFO: Nov 14 10:54:16.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:16.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:16.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:16.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Nov 14 10:54:16.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:16.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:16.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:16.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:16.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:16.010: INFO: Nov 14 10:54:18.023: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:18.023: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:18.023: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:18.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Nov 14 10:54:18.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:18.023: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:18.023: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:18.023: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:18.023: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:18.023: INFO: Nov 14 10:54:20.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:20.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:20.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:20.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Nov 14 10:54:20.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:20.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:20.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:20.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:20.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:20.012: INFO: Nov 14 10:54:22.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:22.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:22.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:22.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Nov 14 10:54:22.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:22.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:22.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:22.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:22.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:22.014: INFO: Nov 14 10:54:24.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:24.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:24.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:24.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Nov 14 10:54:24.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:24.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:24.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:24.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:24.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:24.013: INFO: Nov 14 10:54:26.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:26.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:26.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:26.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Nov 14 10:54:26.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:26.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:26.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:26.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:26.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:26.013: INFO: Nov 14 10:54:28.018: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:28.018: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:28.018: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:28.018: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Nov 14 10:54:28.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:28.018: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:28.018: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:28.018: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:28.018: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:28.018: INFO: Nov 14 10:54:30.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:30.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:30.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:30.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Nov 14 10:54:30.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:30.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:30.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:30.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:30.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:30.014: INFO: Nov 14 10:54:32.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:32.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:32.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:32.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Nov 14 10:54:32.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:32.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:32.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:32.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:32.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:32.009: INFO: Nov 14 10:54:34.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:34.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:34.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:34.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Nov 14 10:54:34.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:34.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:34.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:34.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:34.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:34.012: INFO: Nov 14 10:54:36.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:36.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:36.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:36.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Nov 14 10:54:36.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:36.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:36.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:36.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:36.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:36.013: INFO: Nov 14 10:54:38.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:38.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:38.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:38.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Nov 14 10:54:38.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:38.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:38.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:38.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:38.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:38.012: INFO: Nov 14 10:54:40.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:40.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:40.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:40.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Nov 14 10:54:40.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:40.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:40.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:40.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:40.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:40.009: INFO: Nov 14 10:54:42.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:42.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:42.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:42.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Nov 14 10:54:42.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:42.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:42.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:42.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:42.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:42.011: INFO: Nov 14 10:54:44.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:44.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:44.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:44.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Nov 14 10:54:44.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:44.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:44.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:44.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:44.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:44.013: INFO: Nov 14 10:54:46.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:46.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:46.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:46.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Nov 14 10:54:46.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:46.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:46.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:46.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:46.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:46.013: INFO: Nov 14 10:54:48.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:48.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:48.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:48.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Nov 14 10:54:48.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:48.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:48.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:48.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:48.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:48.013: INFO: Nov 14 10:54:50.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:50.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:50.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:50.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Nov 14 10:54:50.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:50.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:50.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:50.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:50.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:50.010: INFO: Nov 14 10:54:52.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:52.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:52.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:52.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Nov 14 10:54:52.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:52.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:52.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:52.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:52.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:52.013: INFO: Nov 14 10:54:54.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:54.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:54.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:54.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Nov 14 10:54:54.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:54.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:54.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:54.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:54.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:54.008: INFO: Nov 14 10:54:56.016: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:56.016: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:56.016: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:56.016: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Nov 14 10:54:56.016: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:56.016: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:56.016: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:56.016: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:56.016: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:56.016: INFO: Nov 14 10:54:58.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:58.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:58.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:54:58.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Nov 14 10:54:58.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:54:58.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:54:58.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:54:58.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:58.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:54:58.011: INFO: Nov 14 10:55:00.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:00.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:00.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:00.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Nov 14 10:55:00.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:00.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:00.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:00.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:00.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:00.009: INFO: Nov 14 10:55:02.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:02.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:02.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:02.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Nov 14 10:55:02.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:02.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:02.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:02.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:02.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:02.011: INFO: Nov 14 10:55:04.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:04.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:04.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:04.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Nov 14 10:55:04.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:04.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:04.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:04.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:04.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:04.011: INFO: Nov 14 10:55:06.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:06.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:06.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:06.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Nov 14 10:55:06.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:06.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:06.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:06.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:06.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:06.012: INFO: Nov 14 10:55:08.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:08.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:08.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:08.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Nov 14 10:55:08.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:08.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:08.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:08.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:08.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:08.014: INFO: Nov 14 10:55:10.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:10.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:10.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:10.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Nov 14 10:55:10.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:10.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:10.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:10.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:10.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:10.012: INFO: Nov 14 10:55:12.018: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:12.018: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:12.018: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:12.018: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Nov 14 10:55:12.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:12.018: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:12.018: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:12.018: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:12.018: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:12.018: INFO: Nov 14 10:55:14.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:14.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:14.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:14.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Nov 14 10:55:14.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:14.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:14.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:14.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:14.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:14.008: INFO: Nov 14 10:55:16.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:16.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:16.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:16.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Nov 14 10:55:16.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:16.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:16.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:16.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:16.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:16.010: INFO: Nov 14 10:55:18.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:18.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:18.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:18.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Nov 14 10:55:18.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:18.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:18.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:18.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:18.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:18.010: INFO: Nov 14 10:55:20.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:20.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:20.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:20.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Nov 14 10:55:20.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:20.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:20.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:20.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:20.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:20.010: INFO: Nov 14 10:55:22.130: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:22.130: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:22.130: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:22.130: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Nov 14 10:55:22.130: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:22.130: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:22.130: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:22.130: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:22.130: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:22.130: INFO: Nov 14 10:55:24.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:24.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:24.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:24.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Nov 14 10:55:24.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:24.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:24.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:24.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:24.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:24.013: INFO: Nov 14 10:55:26.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:26.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:26.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:26.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Nov 14 10:55:26.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:26.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:26.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:26.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:26.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:26.013: INFO: Nov 14 10:55:28.009: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:28.009: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:28.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:28.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Nov 14 10:55:28.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:28.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:28.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:28.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:28.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:28.009: INFO: Nov 14 10:55:30.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:30.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:30.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:30.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Nov 14 10:55:30.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:30.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:30.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:30.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:30.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:30.010: INFO: Nov 14 10:55:32.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:32.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:32.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:32.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Nov 14 10:55:32.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:32.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:32.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:32.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:32.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:32.010: INFO: Nov 14 10:55:34.020: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:34.020: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:34.020: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:34.020: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Nov 14 10:55:34.020: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:34.020: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:34.020: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:34.020: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:34.020: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:34.020: INFO: Nov 14 10:55:36.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:36.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:36.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:36.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Nov 14 10:55:36.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:36.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:36.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:36.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:36.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:36.010: INFO: Nov 14 10:55:38.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:38.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:38.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:38.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Nov 14 10:55:38.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:38.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:38.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:38.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:38.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:38.008: INFO: Nov 14 10:55:40.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:40.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:40.009: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:40.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Nov 14 10:55:40.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:40.009: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:40.009: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:40.009: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:40.009: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:40.009: INFO: Nov 14 10:55:42.018: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:42.018: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:42.018: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:42.018: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Nov 14 10:55:42.018: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:42.018: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:42.018: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:42.018: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:42.018: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:42.018: INFO: Nov 14 10:55:44.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:44.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:44.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:44.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Nov 14 10:55:44.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:44.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:44.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:44.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:44.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:44.012: INFO: Nov 14 10:55:46.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:46.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:46.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:46.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Nov 14 10:55:46.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:46.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:46.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:46.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:46.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:46.011: INFO: Nov 14 10:55:48.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:48.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:48.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:48.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Nov 14 10:55:48.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:48.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:48.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:48.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:48.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:48.008: INFO: Nov 14 10:55:50.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:50.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:50.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:50.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Nov 14 10:55:50.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:50.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:50.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:50.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:50.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:50.010: INFO: Nov 14 10:55:52.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:52.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:52.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:52.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Nov 14 10:55:52.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:52.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:52.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:52.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:52.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:52.010: INFO: Nov 14 10:55:54.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:54.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:54.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:54.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Nov 14 10:55:54.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:54.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:54.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:54.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:54.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:54.010: INFO: Nov 14 10:55:56.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:56.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:56.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:56.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Nov 14 10:55:56.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:56.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:56.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:56.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:56.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:56.011: INFO: Nov 14 10:55:58.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:58.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:58.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:55:58.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Nov 14 10:55:58.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:55:58.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:55:58.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:55:58.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:58.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:55:58.010: INFO: Nov 14 10:56:00.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:00.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:00.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:00.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Nov 14 10:56:00.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:00.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:00.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:00.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:00.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:00.014: INFO: Nov 14 10:56:02.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:02.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:02.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:02.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Nov 14 10:56:02.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:02.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:02.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:02.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:02.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:02.011: INFO: Nov 14 10:56:04.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:04.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:04.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:04.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Nov 14 10:56:04.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:04.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:04.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:04.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:04.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:04.010: INFO: Nov 14 10:56:06.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:06.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:06.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:06.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Nov 14 10:56:06.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:06.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:06.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:06.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:06.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:06.012: INFO: Nov 14 10:56:08.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:08.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:08.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:08.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Nov 14 10:56:08.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:08.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:08.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:08.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:08.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:08.011: INFO: Nov 14 10:56:10.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:10.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:10.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:10.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Nov 14 10:56:10.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:10.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:10.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:10.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:10.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:10.014: INFO: Nov 14 10:56:12.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:12.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:12.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:12.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Nov 14 10:56:12.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:12.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:12.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:12.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:12.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:12.011: INFO: Nov 14 10:56:14.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:14.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:14.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:14.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Nov 14 10:56:14.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:14.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:14.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:14.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:14.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:14.011: INFO: Nov 14 10:56:16.011: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:16.011: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:16.011: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:16.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Nov 14 10:56:16.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:16.011: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:16.011: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:16.011: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:16.011: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:16.011: INFO: Nov 14 10:56:18.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:18.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:18.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:18.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Nov 14 10:56:18.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:18.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:18.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:18.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:18.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:18.010: INFO: Nov 14 10:56:20.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:20.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:20.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:20.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Nov 14 10:56:20.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:20.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:20.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:20.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:20.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:20.010: INFO: Nov 14 10:56:22.008: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:22.008: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:22.008: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:22.008: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Nov 14 10:56:22.008: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:22.008: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:22.008: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:22.008: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:22.008: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:22.008: INFO: Nov 14 10:56:24.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:24.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:24.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:24.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Nov 14 10:56:24.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:24.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:24.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:24.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:24.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:24.013: INFO: Nov 14 10:56:26.024: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:26.024: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:26.024: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:26.024: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Nov 14 10:56:26.024: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:26.024: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:26.024: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:26.024: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:26.024: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:26.024: INFO: Nov 14 10:56:28.012: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:28.012: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:28.012: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:28.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Nov 14 10:56:28.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:28.012: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:28.012: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:28.012: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:28.012: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:28.012: INFO: Nov 14 10:56:30.014: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:30.014: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:30.014: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:30.014: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Nov 14 10:56:30.014: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:30.014: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:30.014: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:30.014: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:30.014: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:30.014: INFO: Nov 14 10:56:32.013: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:32.013: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:32.013: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:32.013: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Nov 14 10:56:32.013: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:32.013: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:32.013: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:32.013: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:32.013: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:32.013: INFO: Nov 14 10:56:34.010: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:34.010: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:34.010: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:34.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Nov 14 10:56:34.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:34.010: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:34.010: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:34.010: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:34.010: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:34.010: INFO: Nov 14 10:56:34.148: INFO: The status of Pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:34.148: INFO: The status of Pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:34.148: INFO: The status of Pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 14 10:56:34.148: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Nov 14 10:56:34.148: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 14 10:56:34.148: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:34.148: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:34.148: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:34.148: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:34.148: INFO: �[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/14/22 10:56:34.148�[0m �[1mSTEP:�[0m Found 131 events. �[38;5;243m11/14/22 10:56:34.202�[0m Nov 14 10:56:34.202: INFO: At 2022-11-14 10:42:53 +0000 UTC - event for etcd-capz-conf-xrxlyy-control-plane-kzv95: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Container image "registry.k8s.io/etcd:3.5.5-0" already present on machine Nov 14 10:56:34.202: INFO: At 2022-11-14 10:42:53 +0000 UTC - event for kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Container image "gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.65_8e48df13531802" already present on machine Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:01 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-xrxlyy-control-plane-kzv95_5f49ce7c-7a8c-41dd-8479-96598e5193e7 became leader Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:01 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-xrxlyy-control-plane-kzv95_7a38d66e-edba-4478-bf5f-e694e9cbd33f became leader Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:06 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:06 +0000 UTC - event for kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95: {node-controller } NodeNotReady: Node is not ready Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:06 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-9qzx5 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:07 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-kgrp4 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:07 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-wdh72 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:07 +0000 UTC - event for coredns-787d4945fb-kgrp4: {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 14 10:56:34.202: INFO: At 2022-11-14 10:43:07 +0000 UTC - event for coredns-787d4945fb-wdh72: {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 14 10:56:34.202: INFO: At 2022-11-14 10:43:07 +0000 UTC - event for kube-proxy-9qzx5: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-9qzx5 to capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:09 +0000 UTC - event for kube-proxy-9qzx5: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.75_6b0a9ac3015340" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:11 +0000 UTC - event for kube-proxy-9qzx5: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container kube-proxy Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:11 +0000 UTC - event for kube-proxy-9qzx5: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.75_6b0a9ac3015340" in 1.916420998s (1.916429798s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:11 +0000 UTC - event for kube-proxy-9qzx5: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container kube-proxy Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:18 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:18 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-wqzb7 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:18 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {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 14 10:56:34.202: INFO: At 2022-11-14 10:43:19 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:19 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-jb5vc Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:19 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {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 14 10:56:34.202: INFO: At 2022-11-14 10:43:19 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-7vtbt Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:19 +0000 UTC - event for calico-node-7vtbt: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-7vtbt to capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:20 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:25 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 5.500375362s (5.500383562s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:26 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container upgrade-ipam Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:26 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container upgrade-ipam Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:29 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container install-cni Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:29 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container install-cni Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:29 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:32 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-jb5vc to capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:32 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:32 +0000 UTC - event for coredns-787d4945fb-kgrp4: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-kgrp4 to capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:32 +0000 UTC - event for coredns-787d4945fb-wdh72: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-wdh72 to capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:32 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-wqzb7 to capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:33 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {kubelet capz-conf-xrxlyy-control-plane-kzv95} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "183ffb4f4bd9416cf11d551e1919f81eb4f53047d52e7df5b89c6d3ad9740e02": 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 14 10:56:34.202: INFO: At 2022-11-14 10:43:33 +0000 UTC - event for coredns-787d4945fb-kgrp4: {kubelet capz-conf-xrxlyy-control-plane-kzv95} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c99f36294570f91454b382a5d4021a7edd3457b1c45fb14d1c644909c4e71412": 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 14 10:56:34.202: INFO: At 2022-11-14 10:43:33 +0000 UTC - event for coredns-787d4945fb-wdh72: {kubelet capz-conf-xrxlyy-control-plane-kzv95} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d7d7fae3f52c4e18fcfd0210f560d2f59f7664343436a57ccda2909de6845bf6": 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 14 10:56:34.202: INFO: At 2022-11-14 10:43:33 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {kubelet capz-conf-xrxlyy-control-plane-kzv95} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a30140fe58a487ad4a2e9680f5c8436a8db812ee58aa7073e2312475f72cd3ef": 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 14 10:56:34.202: INFO: At 2022-11-14 10:43:39 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.925060887s (6.925067888s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:39 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container calico-node Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:39 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container calico-node Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:40 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} 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 14 10:56:34.202: INFO: At 2022-11-14 10:43:41 +0000 UTC - event for calico-node-7vtbt: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:45 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:45 +0000 UTC - event for coredns-787d4945fb-kgrp4: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:45 +0000 UTC - event for coredns-787d4945fb-kgrp4: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Unhealthy: Readiness probe failed: Get "http://192.168.108.195:8181/ready": dial tcp 192.168.108.195:8181: connect: connection refused Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:45 +0000 UTC - event for coredns-787d4945fb-kgrp4: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container coredns Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:45 +0000 UTC - event for coredns-787d4945fb-kgrp4: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container coredns Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:45 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:47 +0000 UTC - event for coredns-787d4945fb-wdh72: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:47 +0000 UTC - event for coredns-787d4945fb-wdh72: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container coredns Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:48 +0000 UTC - event for coredns-787d4945fb-wdh72: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container coredns Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:50 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.810030174s (5.810165768s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:50 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container calico-kube-controllers Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:51 +0000 UTC - event for calico-kube-controllers-657b584867-jb5vc: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container calico-kube-controllers Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:54 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Created: Created container metrics-server Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:54 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.828200723s (9.573784686s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:43:54 +0000 UTC - event for metrics-server-c9574f845-wqzb7: {kubelet capz-conf-xrxlyy-control-plane-kzv95} Started: Started container metrics-server Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-q6n7j Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for calico-node-windows-q6n7j: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-q6n7j to capz-conf-8wgrz Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-6prt7 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for containerd-logger-6prt7: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-6prt7 to capz-conf-8wgrz Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-8dhcv Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for kube-proxy-windows-8dhcv: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-8dhcv to capz-conf-8wgrz Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:34 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-z9p5p Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:34 +0000 UTC - event for calico-node-windows-z9p5p: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-z9p5p to capz-conf-xh5kn Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:34 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-jjdf5 Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:34 +0000 UTC - event for containerd-logger-jjdf5: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-jjdf5 to capz-conf-xh5kn Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:34 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-hb58v Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:34 +0000 UTC - event for kube-proxy-windows-hb58v: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-hb58v to capz-conf-xh5kn Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:35 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:35 +0000 UTC - event for kube-proxy-windows-8dhcv: {kubelet capz-conf-8wgrz} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unavailable desc = error reading from server: EOF Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} FailedMount: MountVolume.SetUp failed for volume "calico-config-windows" : failed to sync configmap cache: timed out waiting for the condition Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for containerd-logger-6prt7: {kubelet capz-conf-8wgrz} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unavailable desc = error reading from server: EOF Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for containerd-logger-jjdf5: {kubelet capz-conf-xh5kn} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for kube-proxy-windows-8dhcv: {kubelet capz-conf-8wgrz} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing open //./pipe/containerd-containerd: The system cannot find the file specified." Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:50 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:50 +0000 UTC - event for containerd-logger-jjdf5: {kubelet capz-conf-xh5kn} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:50 +0000 UTC - event for kube-proxy-windows-hb58v: {kubelet capz-conf-xh5kn} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:50 +0000 UTC - event for kube-proxy-windows-hb58v: {kubelet capz-conf-xh5kn} Created: Created container kube-proxy Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:50 +0000 UTC - event for kube-proxy-windows-hb58v: {kubelet capz-conf-xh5kn} Started: Started container kube-proxy Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:53 +0000 UTC - event for containerd-logger-jjdf5: {kubelet capz-conf-xh5kn} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 2.9898864s (2.9898864s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:57 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.3145717s (7.3044581s including waiting) Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:57 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Created: Created container install-cni Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:57 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Started: Started container install-cni Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:59 +0000 UTC - event for containerd-logger-jjdf5: {kubelet capz-conf-xh5kn} Created: Created container containerd-logger Nov 14 10:56:34.202: INFO: At 2022-11-14 10:45:59 +0000 UTC - event for containerd-logger-jjdf5: {kubelet capz-conf-xh5kn} Started: Started container containerd-logger Nov 14 10:56:34.203: INFO: At 2022-11-14 10:45:59 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-xfkq8 Nov 14 10:56:34.203: INFO: At 2022-11-14 10:45:59 +0000 UTC - event for csi-proxy-xfkq8: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-xfkq8 to capz-conf-xh5kn Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:00 +0000 UTC - event for csi-proxy-xfkq8: {kubelet capz-conf-xh5kn} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:02 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:06 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:06 +0000 UTC - event for containerd-logger-6prt7: {kubelet capz-conf-8wgrz} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:06 +0000 UTC - event for kube-proxy-windows-8dhcv: {kubelet capz-conf-8wgrz} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:06 +0000 UTC - event for kube-proxy-windows-8dhcv: {kubelet capz-conf-8wgrz} Created: Created container kube-proxy Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:06 +0000 UTC - event for kube-proxy-windows-8dhcv: {kubelet capz-conf-8wgrz} Started: Started container kube-proxy Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:09 +0000 UTC - event for containerd-logger-6prt7: {kubelet capz-conf-8wgrz} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 2.878898s (2.8793958s including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:12 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Created: Created container install-cni Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:12 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 3.36901s (6.2414113s including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:13 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Started: Started container install-cni Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:13 +0000 UTC - event for csi-proxy-xfkq8: {kubelet capz-conf-xh5kn} Created: Created container csi-proxy Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:13 +0000 UTC - event for csi-proxy-xfkq8: {kubelet capz-conf-xh5kn} Started: Started container csi-proxy Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:13 +0000 UTC - event for csi-proxy-xfkq8: {kubelet capz-conf-xh5kn} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 13.197141s (13.197141s including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:14 +0000 UTC - event for containerd-logger-6prt7: {kubelet capz-conf-8wgrz} Created: Created container containerd-logger Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:14 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-fmhz4 Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:14 +0000 UTC - event for csi-proxy-fmhz4: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-fmhz4 to capz-conf-8wgrz Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:15 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 2.3940801s (13.2007155s including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:15 +0000 UTC - event for containerd-logger-6prt7: {kubelet capz-conf-8wgrz} Started: Started container containerd-logger Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:15 +0000 UTC - event for csi-proxy-fmhz4: {kubelet capz-conf-8wgrz} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:16 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 276.4951ms (276.4951ms including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:16 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Created: Created container calico-node-startup Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:16 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Started: Started container calico-node-startup Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:16 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:18 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:21 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Created: Created container calico-node-felix Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:21 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Started: Started container calico-node-felix Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:28 +0000 UTC - event for csi-proxy-fmhz4: {kubelet capz-conf-8wgrz} Started: Started container csi-proxy Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:28 +0000 UTC - event for csi-proxy-fmhz4: {kubelet capz-conf-8wgrz} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 12.6835211s (12.6836996s including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:28 +0000 UTC - event for csi-proxy-fmhz4: {kubelet capz-conf-8wgrz} Created: Created container csi-proxy Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:30 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 2.4912516s (12.7818636s including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:30 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Created: Created container calico-node-startup Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:31 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Started: Started container calico-node-startup Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:31 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 274.4828ms (274.4828ms including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:31 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess" Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:36 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Created: Created container calico-node-felix Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:36 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Started: Started container calico-node-felix Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:43 +0000 UTC - event for calico-node-windows-z9p5p: {kubelet capz-conf-xh5kn} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 285.4545ms (285.4545ms including waiting) Nov 14 10:56:34.203: INFO: At 2022-11-14 10:46:58 +0000 UTC - event for calico-node-windows-q6n7j: {kubelet capz-conf-8wgrz} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 258.3325ms (258.3325ms including waiting) Nov 14 10:56:34.263: INFO: POD NODE PHASE GRACE CONDITIONS Nov 14 10:56:34.263: INFO: calico-kube-controllers-657b584867-jb5vc capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC }] Nov 14 10:56:34.263: INFO: calico-node-7vtbt capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:19 +0000 UTC }] Nov 14 10:56:34.263: INFO: calico-node-windows-q6n7j capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:18 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:47:04 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:47:04 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:56:34.263: INFO: calico-node-windows-z9p5p capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:02 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:49 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:49 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC }] Nov 14 10:56:34.263: INFO: containerd-logger-6prt7 capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:15 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:15 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:56:34.263: INFO: containerd-logger-jjdf5 capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC }] Nov 14 10:56:34.263: INFO: coredns-787d4945fb-kgrp4 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC }] Nov 14 10:56:34.263: INFO: coredns-787d4945fb-wdh72 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC }] Nov 14 10:56:34.263: INFO: csi-proxy-fmhz4 capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:14 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:14 +0000 UTC }] Nov 14 10:56:34.264: INFO: csi-proxy-xfkq8 capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:59 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:14 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:14 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:59 +0000 UTC }] Nov 14 10:56:34.264: INFO: etcd-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:05 +0000 UTC }] Nov 14 10:56:34.264: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:45 +0000 UTC }] Nov 14 10:56:34.264: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:34.264: INFO: kube-proxy-9qzx5 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:07 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:06 +0000 UTC }] Nov 14 10:56:34.264: INFO: kube-proxy-windows-8dhcv capz-conf-8wgrz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:06 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:33 +0000 UTC }] Nov 14 10:56:34.264: INFO: kube-proxy-windows-hb58v capz-conf-xh5kn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC }] Nov 14 10:56:34.264: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Nov 14 10:56:34.264: INFO: metrics-server-c9574f845-wqzb7 capz-conf-xrxlyy-control-plane-kzv95 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:43:32 +0000 UTC }] Nov 14 10:56:34.264: INFO: Nov 14 10:56:34.724: INFO: Logging node info for node capz-conf-8wgrz Nov 14 10:56:34.914: INFO: Node Info: &Node{ObjectMeta:{capz-conf-8wgrz ae7d3192-2804-47a1-83e4-6beb625e7b39 1551 0 2022-11-14 10:45:33 +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:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-8wgrz kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-xrxlyy cluster.x-k8s.io/cluster-namespace:capz-conf-xrxlyy cluster.x-k8s.io/machine:capz-conf-xrxlyy-md-win-7f68499d6b-ct7b8 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-xrxlyy-md-win-7f68499d6b 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.102.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:ee:d0:4a volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-14 10:45:33 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-14 10:45:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-14 10:46:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 10:46:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-14 10:46:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-14 10:51:40 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:nodeInfo":{"f:containerRuntimeVersion":{}}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-xrxlyy/providers/Microsoft.Compute/virtualMachines/capz-conf-8wgrz,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-14 10:51:40 +0000 UTC,LastTransitionTime:2022-11-14 10:45:33 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 10:51:40 +0000 UTC,LastTransitionTime:2022-11-14 10:45:33 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 10:51:40 +0000 UTC,LastTransitionTime:2022-11-14 10:45:33 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 10:51:40 +0000 UTC,LastTransitionTime:2022-11-14 10:46:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-8wgrz,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-8wgrz,SystemUUID:B626C0BD-2BE4-4ECD-9ABC-55B2ADDCE65F,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.75+6b0a9ac3015340-dirty,KubeProxyVersion:v1.26.0-beta.0.75+6b0a9ac3015340-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Nov 14 10:56:34.914: INFO: Logging kubelet events for node capz-conf-8wgrz Nov 14 10:56:35.111: INFO: Logging pods the kubelet thinks is on node capz-conf-8wgrz Nov 14 10:56:35.328: INFO: containerd-logger-6prt7 started at 2022-11-14 10:45:34 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:35.328: INFO: Container containerd-logger ready: true, restart count 0 Nov 14 10:56:35.328: INFO: kube-proxy-windows-8dhcv started at 2022-11-14 10:45:34 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:35.328: INFO: Container kube-proxy ready: true, restart count 0 Nov 14 10:56:35.328: INFO: calico-node-windows-q6n7j started at 2022-11-14 10:45:34 +0000 UTC (1+2 container statuses recorded) Nov 14 10:56:35.328: INFO: Init container install-cni ready: true, restart count 0 Nov 14 10:56:35.328: INFO: Container calico-node-felix ready: true, restart count 1 Nov 14 10:56:35.328: INFO: Container calico-node-startup ready: true, restart count 0 Nov 14 10:56:35.328: INFO: csi-proxy-fmhz4 started at 2022-11-14 10:46:14 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:35.328: INFO: Container csi-proxy ready: true, restart count 0 Nov 14 10:56:35.958: INFO: Latency metrics for node capz-conf-8wgrz Nov 14 10:56:35.958: INFO: Logging node info for node capz-conf-xh5kn Nov 14 10:56:36.113: INFO: Node Info: &Node{ObjectMeta:{capz-conf-xh5kn 0bb215c3-9273-4253-af1d-937f99ee0512 1552 0 2022-11-14 10:45:34 +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:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-xh5kn kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-xrxlyy cluster.x-k8s.io/cluster-namespace:capz-conf-xrxlyy cluster.x-k8s.io/machine:capz-conf-xrxlyy-md-win-7f68499d6b-2jhd6 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-xrxlyy-md-win-7f68499d6b 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.154.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:6e:6b:a4 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-14 10:45:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-14 10:45:34 +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-14 10:45:59 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 10:46:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-14 10:46:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-14 10:51:41 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-xrxlyy/providers/Microsoft.Compute/virtualMachines/capz-conf-xh5kn,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-14 10:51:41 +0000 UTC,LastTransitionTime:2022-11-14 10:45:34 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 10:51:41 +0000 UTC,LastTransitionTime:2022-11-14 10:45:34 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 10:51:41 +0000 UTC,LastTransitionTime:2022-11-14 10:45:34 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 10:51:41 +0000 UTC,LastTransitionTime:2022-11-14 10:45:59 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-xh5kn,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-xh5kn,SystemUUID:8BCCF234-7CC9-4A62-A014-2975DE6B2579,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.75+6b0a9ac3015340-dirty,KubeProxyVersion:v1.26.0-beta.0.75+6b0a9ac3015340-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Nov 14 10:56:36.113: INFO: Logging kubelet events for node capz-conf-xh5kn Nov 14 10:56:36.319: INFO: Logging pods the kubelet thinks is on node capz-conf-xh5kn Nov 14 10:56:36.527: INFO: csi-proxy-xfkq8 started at 2022-11-14 10:45:59 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:36.527: INFO: Container csi-proxy ready: true, restart count 0 Nov 14 10:56:36.527: INFO: calico-node-windows-z9p5p started at 2022-11-14 10:45:35 +0000 UTC (1+2 container statuses recorded) Nov 14 10:56:36.527: INFO: Init container install-cni ready: true, restart count 0 Nov 14 10:56:36.527: INFO: Container calico-node-felix ready: true, restart count 1 Nov 14 10:56:36.527: INFO: Container calico-node-startup ready: true, restart count 0 Nov 14 10:56:36.527: INFO: containerd-logger-jjdf5 started at 2022-11-14 10:45:35 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:36.527: INFO: Container containerd-logger ready: true, restart count 0 Nov 14 10:56:36.527: INFO: kube-proxy-windows-hb58v started at 2022-11-14 10:45:35 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:36.527: INFO: Container kube-proxy ready: true, restart count 0 Nov 14 10:56:37.157: INFO: Latency metrics for node capz-conf-xh5kn Nov 14 10:56:37.157: INFO: Logging node info for node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:37.314: INFO: Node Info: &Node{ObjectMeta:{capz-conf-xrxlyy-control-plane-kzv95 fe3053c0-bd72-4e9a-a3f8-5b12f35a9dd2 1788 0 2022-11-14 10:43:00 +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:eastus2 failure-domain.beta.kubernetes.io/zone:eastus2-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-xrxlyy-control-plane-kzv95 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:eastus2 topology.kubernetes.io/zone:eastus2-3] map[cluster.x-k8s.io/cluster-name:capz-conf-xrxlyy cluster.x-k8s.io/cluster-namespace:capz-conf-xrxlyy cluster.x-k8s.io/machine:capz-conf-xrxlyy-control-plane-d8lkg cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-xrxlyy-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.108.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-14 10:43:00 +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-14 10:43:03 +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-14 10:43:16 +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-14 10:43:32 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-14 10:43:40 +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-14 10:54:18 +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-xrxlyy/providers/Microsoft.Compute/virtualMachines/capz-conf-xrxlyy-control-plane-kzv95,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-14 10:43:40 +0000 UTC,LastTransitionTime:2022-11-14 10:43:40 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-14 10:54:18 +0000 UTC,LastTransitionTime:2022-11-14 10:42:45 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 10:54:18 +0000 UTC,LastTransitionTime:2022-11-14 10:42:45 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 10:54:18 +0000 UTC,LastTransitionTime:2022-11-14 10:42:45 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 10:54:18 +0000 UTC,LastTransitionTime:2022-11-14 10:43:32 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-xrxlyy-control-plane-kzv95,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:0c2a847301db4555bd34b3d36da43772,SystemUUID:05284e43-1c64-e149-83c7-7778e53909b3,BootID:8bbf89ce-b8a9-4fe4-9e6d-b63a34b5943f,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.75+6b0a9ac3015340,KubeProxyVersion:v1.26.0-beta.0.75+6b0a9ac3015340,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:b83c1d70989e1fe87583607bf5aee1ee34e52773d4755b95f5cf5a451962f3a4 registry.k8s.io/etcd:3.5.5-0],SizeBytes:102417044,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:6f72b851544986cb0921b53ea655ec04c36131248f16d4ad110cb3ca0c369dc1 registry.k8s.io/etcd:3.5.4-0],SizeBytes:102157811,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:78bc199299f966b0694dc4044501aee2d7ebd6862b2b0a00bca3ee8d3813c82f docker.io/calico/kube-controllers:v3.23.0],SizeBytes:56343954,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:ec69d1434d36d220ed8080dce242380284d4166daacb073dbc6d82e11bb1d9c4 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:35316538,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:4188262a351f156e8027ff81693d771c35b34b668cbd61e59c4a4490dd5c08f3 registry.k8s.io/kube-apiserver:v1.25.3],SizeBytes:34238163,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:bca35bdba72c14884db646f3bbf5334247c840b47a196ba6aad1bd4a8481bef0 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:32240596,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:d3a06262256f3e7578d5f77df137a8cdf58f9f498f35b5b56d116e8a7e31dc91 registry.k8s.io/kube-controller-manager:v1.25.3],SizeBytes:31261869,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:fbd439680dd72c3e4facc929a7a135d11fbf949e2099357d50b28132d086ccd9 gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:21534778,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:77f27889c1e9f75e4fe598c2af0a4591a0f6f5d9a2ebd530823d584ac6aa3758 capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.75_6b0a9ac3015340],SizeBytes:21532917,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:6bf25f038543e1f433cb7f2bdda445ed348c7b9279935ebc2ae4f432308ed82f registry.k8s.io/kube-proxy:v1.25.3],SizeBytes:20265805,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:ba0a3921d93c8461119feb344fd9341c2e128206857da6ad515d5da42378e9b1 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:17482660,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Nov 14 10:56:37.314: INFO: Logging kubelet events for node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:37.510: INFO: Logging pods the kubelet thinks is on node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:37.748: INFO: coredns-787d4945fb-wdh72 started at 2022-11-14 10:43:32 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Container coredns ready: true, restart count 0 Nov 14 10:56:37.748: INFO: kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 started at <nil> (0+0 container statuses recorded) Nov 14 10:56:37.748: INFO: etcd-capz-conf-xrxlyy-control-plane-kzv95 started at 2022-11-14 10:43:05 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Container etcd ready: true, restart count 0 Nov 14 10:56:37.748: INFO: calico-kube-controllers-657b584867-jb5vc started at 2022-11-14 10:43:32 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Container calico-kube-controllers ready: true, restart count 0 Nov 14 10:56:37.748: INFO: calico-node-7vtbt started at 2022-11-14 10:43:19 +0000 UTC (2+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Init container upgrade-ipam ready: true, restart count 0 Nov 14 10:56:37.748: INFO: Init container install-cni ready: true, restart count 0 Nov 14 10:56:37.748: INFO: Container calico-node ready: true, restart count 0 Nov 14 10:56:37.748: INFO: coredns-787d4945fb-kgrp4 started at 2022-11-14 10:43:32 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Container coredns ready: true, restart count 0 Nov 14 10:56:37.748: INFO: metrics-server-c9574f845-wqzb7 started at 2022-11-14 10:43:32 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Container metrics-server ready: true, restart count 0 Nov 14 10:56:37.748: INFO: kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95 started at <nil> (0+0 container statuses recorded) Nov 14 10:56:37.748: INFO: kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 started at <nil> (0+0 container statuses recorded) Nov 14 10:56:37.748: INFO: kube-proxy-9qzx5 started at 2022-11-14 10:43:07 +0000 UTC (0+1 container statuses recorded) Nov 14 10:56:37.748: INFO: Container kube-proxy ready: true, restart count 0 Nov 14 10:56:38.358: INFO: Latency metrics for node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:38.528: INFO: Running kubectl logs on non-ready containers in kube-system Nov 14 10:56:38.910: INFO: Failed to get logs of pod kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95) Nov 14 10:56:38.910: INFO: Logs of kube-system/kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95:kube-apiserver on node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:38.910: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-xrxlyy-control-plane-kzv95:kube-apiserver Nov 14 10:56:39.310: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95) Nov 14 10:56:39.310: INFO: Logs of kube-system/kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95:kube-controller-manager on node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:39.310: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95:kube-controller-manager Nov 14 10:56:39.712: INFO: Failed to get logs of pod kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95) Nov 14 10:56:39.712: INFO: Logs of kube-system/kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95:kube-scheduler on node capz-conf-xrxlyy-control-plane-kzv95 Nov 14 10:56:39.712: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95:kube-scheduler Nov 14 10:56:39.713: 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-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-11-14 10:42:45 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-11-14 10:43:06 +0000 UTC Reason: Message:} {Type:ContainersReady Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-11-14 10:43:03 +0000 UTC Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-11-14 10:42:45 +0000 UTC Reason: Message:}] kube-controller-manager-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] kube-scheduler-capz-conf-xrxlyy-control-plane-kzv95 capz-conf-xrxlyy-control-plane-kzv95 Pending [] Full Stack Trace k8s.io/kubernetes/test/e2e.setupSuite() test/e2e/e2e.go:249 +0x4de k8s.io/kubernetes/test/e2e.glob..func1() test/e2e/e2e.go:81 +0x8f reflect.Value.call({0x669fa40?, 0x788a190?, 0x13?}, {0x75ac456, 0x4}, {0xc00088ff20, 0x0, 0x0?}) /usr/local/go/src/reflect/value.go:584 +0x8c5 reflect.Value.Call({0x669fa40?, 0x788a190?, 0x26cb5ed?}, {0xc000420720?, 0x2659b67?, 0xc000420720?}) /usr/local/go/src/reflect/value.go:368 +0xbc
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e Conformance Tests conformance-tests
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