PR #107826 pull-kubernetes-e2e-capz-conformance #1616529477456629760
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | smarterclayton: wait: Introduce new methods that allow detection of context cancellation |
| Result | SUCCESS |
| Tests | 25 failed / 28 succeeded |
| Started | |
| Elapsed | 54m46s |
| Revision | 0a317ecc039c2a4577e3a8cdf37c8af42ebd6686 |
| Refs |
107826 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.464from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.464
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.47from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.47
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.462from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.462
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.462from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.462
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.466from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.466
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.465from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.465
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.461from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.461
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.45from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.45
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.455from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.455
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.45from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.45
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.459from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.459
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\]$'
[FAILED] Error waiting for all pods to be running and ready: 3 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD NODE PHASE GRACE CONDITIONS
kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-scheduler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-scheduler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason: Message:}]
In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/20/23 21:03:40.38
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/20/23 20:53:04.465
Jan 20 20:53:04.466: INFO: >>> kubeConfig: /tmp/kubeconfig
Jan 20 20:53:04.469: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Jan 20 20:53:04.704: INFO: Condition Ready of node capz-conf-4dba30-md-0-jzskz is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-20 20:52:57 +0000 UTC}]. Failure
Jan 20 20:53:04.704: INFO: Condition Ready of node capz-conf-4dba30-md-0-kbtgj is true, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoExecute 2023-01-20 20:52:47 +0000 UTC}]. Failure
Jan 20 20:53:04.704: INFO: Unschedulable nodes= 2, maximum value for starting tests= 0
Jan 20 20:53:04.704: INFO: -> Node capz-conf-4dba30-md-0-jzskz [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-20 20:52:57 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
Jan 20 20:53:04.704: INFO: -> Node capz-conf-4dba30-md-0-kbtgj [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready NoExecute 2023-01-20 20:52:47 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
Jan 20 20:53:04.704: INFO: ==== node wait: 1 out of 3 nodes are ready, max notReady allowed 0. Need 2 more before starting.
Jan 20 20:53:34.753: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Jan 20 20:53:34.943: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:34.943: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:34.943: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:34.943: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Jan 20 20:53:34.943: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:34.943: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:34.943: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:34.943: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:34.943: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:34.943: INFO:
Jan 20 20:53:37.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:37.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:37.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:37.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Jan 20 20:53:37.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:37.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:37.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:37.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:37.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:37.076: INFO:
Jan 20 20:53:39.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:39.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:39.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:39.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Jan 20 20:53:39.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:39.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:39.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:39.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:39.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:39.071: INFO:
Jan 20 20:53:41.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:41.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:41.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:41.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Jan 20 20:53:41.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:41.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:41.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:41.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:41.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:41.070: INFO:
Jan 20 20:53:43.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:43.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:43.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:43.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Jan 20 20:53:43.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:43.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:43.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:43.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:43.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:43.070: INFO:
Jan 20 20:53:45.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:45.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:45.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:45.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Jan 20 20:53:45.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:45.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:45.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:45.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:45.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:45.078: INFO:
Jan 20 20:53:47.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:47.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:47.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:47.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Jan 20 20:53:47.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:47.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:47.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:47.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:47.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:47.071: INFO:
Jan 20 20:53:49.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:49.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:49.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:49.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Jan 20 20:53:49.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:49.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:49.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:49.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:49.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:49.074: INFO:
Jan 20 20:53:51.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:51.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:51.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:51.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Jan 20 20:53:51.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:51.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:51.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:51.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:51.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:51.071: INFO:
Jan 20 20:53:53.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:53.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:53.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:53.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Jan 20 20:53:53.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:53.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:53.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:53.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:53.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:53.071: INFO:
Jan 20 20:53:55.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:55.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:55.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:55.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Jan 20 20:53:55.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:55.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:55.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:55.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:55.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:55.069: INFO:
Jan 20 20:53:57.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:57.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:57.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:57.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Jan 20 20:53:57.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:57.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:57.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:57.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:57.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:57.073: INFO:
Jan 20 20:53:59.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:59.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:59.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:53:59.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Jan 20 20:53:59.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:53:59.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:53:59.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:59.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:53:59.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:53:59.068: INFO:
Jan 20 20:54:01.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:01.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:01.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:01.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Jan 20 20:54:01.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:01.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:01.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:01.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:01.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:01.070: INFO:
Jan 20 20:54:03.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:03.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:03.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:03.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Jan 20 20:54:03.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:03.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:03.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:03.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:03.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:03.068: INFO:
Jan 20 20:54:05.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:05.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:05.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:05.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Jan 20 20:54:05.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:05.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:05.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:05.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:05.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:05.068: INFO:
Jan 20 20:54:07.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:07.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:07.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:07.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Jan 20 20:54:07.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:07.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:07.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:07.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:07.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:07.071: INFO:
Jan 20 20:54:09.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:09.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:09.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:09.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Jan 20 20:54:09.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:09.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:09.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:09.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:09.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:09.069: INFO:
Jan 20 20:54:11.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:11.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:11.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:11.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Jan 20 20:54:11.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:11.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:11.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:11.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:11.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:11.071: INFO:
Jan 20 20:54:13.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:13.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:13.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:13.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Jan 20 20:54:13.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:13.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:13.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:13.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:13.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:13.071: INFO:
Jan 20 20:54:15.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:15.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:15.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:15.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Jan 20 20:54:15.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:15.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:15.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:15.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:15.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:15.068: INFO:
Jan 20 20:54:17.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:17.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:17.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:17.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Jan 20 20:54:17.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:17.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:17.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:17.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:17.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:17.073: INFO:
Jan 20 20:54:19.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:19.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:19.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:19.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Jan 20 20:54:19.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:19.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:19.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:19.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:19.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:19.073: INFO:
Jan 20 20:54:21.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:21.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:21.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:21.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Jan 20 20:54:21.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:21.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:21.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:21.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:21.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:21.072: INFO:
Jan 20 20:54:23.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:23.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:23.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:23.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Jan 20 20:54:23.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:23.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:23.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:23.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:23.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:23.069: INFO:
Jan 20 20:54:25.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:25.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:25.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:25.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Jan 20 20:54:25.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:25.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:25.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:25.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:25.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:25.071: INFO:
Jan 20 20:54:27.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:27.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:27.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:27.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Jan 20 20:54:27.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:27.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:27.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:27.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:27.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:27.071: INFO:
Jan 20 20:54:29.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:29.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:29.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:29.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Jan 20 20:54:29.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:29.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:29.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:29.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:29.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:29.072: INFO:
Jan 20 20:54:31.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:31.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:31.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:31.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Jan 20 20:54:31.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:31.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:31.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:31.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:31.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:31.068: INFO:
Jan 20 20:54:33.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:33.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:33.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:33.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Jan 20 20:54:33.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:33.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:33.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:33.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:33.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:33.072: INFO:
Jan 20 20:54:35.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:35.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:35.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:35.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Jan 20 20:54:35.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:35.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:35.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:35.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:35.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:35.071: INFO:
Jan 20 20:54:37.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:37.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:37.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:37.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Jan 20 20:54:37.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:37.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:37.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:37.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:37.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:37.072: INFO:
Jan 20 20:54:39.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:39.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:39.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:39.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Jan 20 20:54:39.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:39.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:39.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:39.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:39.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:39.069: INFO:
Jan 20 20:54:41.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:41.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:41.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:41.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Jan 20 20:54:41.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:41.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:41.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:41.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:41.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:41.070: INFO:
Jan 20 20:54:43.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:43.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:43.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:43.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Jan 20 20:54:43.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:43.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:43.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:43.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:43.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:43.070: INFO:
Jan 20 20:54:45.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:45.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:45.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:45.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Jan 20 20:54:45.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:45.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:45.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:45.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:45.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:45.071: INFO:
Jan 20 20:54:47.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:47.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:47.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:47.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Jan 20 20:54:47.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:47.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:47.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:47.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:47.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:47.070: INFO:
Jan 20 20:54:49.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:49.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:49.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:49.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Jan 20 20:54:49.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:49.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:49.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:49.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:49.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:49.073: INFO:
Jan 20 20:54:51.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:51.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:51.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:51.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Jan 20 20:54:51.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:51.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:51.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:51.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:51.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:51.069: INFO:
Jan 20 20:54:53.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:53.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:53.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:53.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Jan 20 20:54:53.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:53.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:53.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:53.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:53.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:53.072: INFO:
Jan 20 20:54:55.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:55.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:55.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:55.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Jan 20 20:54:55.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:55.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:55.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:55.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:55.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:55.068: INFO:
Jan 20 20:54:57.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:57.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:57.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:57.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Jan 20 20:54:57.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:57.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:57.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:57.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:57.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:57.069: INFO:
Jan 20 20:54:59.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:59.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:59.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:54:59.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Jan 20 20:54:59.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:54:59.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:54:59.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:59.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:54:59.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:54:59.077: INFO:
Jan 20 20:55:01.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:01.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:01.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:01.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Jan 20 20:55:01.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:01.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:01.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:01.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:01.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:01.073: INFO:
Jan 20 20:55:03.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:03.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:03.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:03.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Jan 20 20:55:03.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:03.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:03.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:03.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:03.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:03.070: INFO:
Jan 20 20:55:05.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:05.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:05.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:05.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Jan 20 20:55:05.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:05.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:05.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:05.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:05.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:05.068: INFO:
Jan 20 20:55:07.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:07.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:07.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:07.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Jan 20 20:55:07.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:07.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:07.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:07.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:07.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:07.069: INFO:
Jan 20 20:55:09.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:09.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:09.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:09.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Jan 20 20:55:09.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:09.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:09.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:09.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:09.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:09.071: INFO:
Jan 20 20:55:11.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:11.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:11.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:11.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Jan 20 20:55:11.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:11.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:11.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:11.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:11.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:11.075: INFO:
Jan 20 20:55:13.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:13.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:13.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:13.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Jan 20 20:55:13.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:13.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:13.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:13.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:13.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:13.071: INFO:
Jan 20 20:55:15.081: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:15.081: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:15.081: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:15.081: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Jan 20 20:55:15.081: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:15.081: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:15.081: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:15.081: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:15.081: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:15.081: INFO:
Jan 20 20:55:17.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:17.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:17.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:17.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Jan 20 20:55:17.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:17.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:17.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:17.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:17.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:17.073: INFO:
Jan 20 20:55:19.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:19.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:19.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:19.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Jan 20 20:55:19.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:19.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:19.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:19.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:19.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:19.070: INFO:
Jan 20 20:55:21.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:21.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:21.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:21.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Jan 20 20:55:21.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:21.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:21.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:21.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:21.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:21.076: INFO:
Jan 20 20:55:23.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:23.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:23.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:23.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Jan 20 20:55:23.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:23.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:23.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:23.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:23.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:23.073: INFO:
Jan 20 20:55:25.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:25.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:25.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:25.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Jan 20 20:55:25.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:25.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:25.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:25.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:25.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:25.075: INFO:
Jan 20 20:55:27.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:27.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:27.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:27.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Jan 20 20:55:27.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:27.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:27.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:27.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:27.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:27.070: INFO:
Jan 20 20:55:29.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:29.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:29.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:29.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Jan 20 20:55:29.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:29.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:29.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:29.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:29.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:29.070: INFO:
Jan 20 20:55:31.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:31.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:31.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:31.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Jan 20 20:55:31.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:31.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:31.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:31.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:31.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:31.069: INFO:
Jan 20 20:55:33.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:33.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:33.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:33.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Jan 20 20:55:33.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:33.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:33.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:33.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:33.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:33.071: INFO:
Jan 20 20:55:35.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:35.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:35.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:35.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Jan 20 20:55:35.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:35.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:35.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:35.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:35.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:35.069: INFO:
Jan 20 20:55:37.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:37.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:37.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:37.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Jan 20 20:55:37.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:37.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:37.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:37.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:37.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:37.069: INFO:
Jan 20 20:55:39.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:39.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:39.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:39.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Jan 20 20:55:39.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:39.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:39.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:39.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:39.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:39.070: INFO:
Jan 20 20:55:41.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:41.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:41.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:41.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Jan 20 20:55:41.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:41.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:41.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:41.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:41.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:41.071: INFO:
Jan 20 20:55:43.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:43.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:43.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:43.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Jan 20 20:55:43.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:43.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:43.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:43.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:43.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:43.069: INFO:
Jan 20 20:55:45.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:45.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:45.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:45.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Jan 20 20:55:45.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:45.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:45.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:45.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:45.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:45.068: INFO:
Jan 20 20:55:47.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:47.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:47.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:47.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Jan 20 20:55:47.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:47.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:47.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:47.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:47.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:47.069: INFO:
Jan 20 20:55:49.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:49.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:49.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:49.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Jan 20 20:55:49.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:49.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:49.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:49.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:49.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:49.069: INFO:
Jan 20 20:55:51.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:51.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:51.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:51.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Jan 20 20:55:51.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:51.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:51.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:51.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:51.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:51.070: INFO:
Jan 20 20:55:53.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:53.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:53.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:53.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Jan 20 20:55:53.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:53.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:53.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:53.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:53.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:53.074: INFO:
Jan 20 20:55:55.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:55.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:55.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:55.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Jan 20 20:55:55.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:55.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:55.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:55.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:55.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:55.070: INFO:
Jan 20 20:55:57.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:57.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:57.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:57.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Jan 20 20:55:57.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:57.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:57.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:57.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:57.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:57.069: INFO:
Jan 20 20:55:59.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:59.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:59.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:55:59.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Jan 20 20:55:59.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:55:59.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:55:59.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:59.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:55:59.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:55:59.069: INFO:
Jan 20 20:56:01.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:01.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:01.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:01.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Jan 20 20:56:01.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:01.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:01.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:01.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:01.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:01.070: INFO:
Jan 20 20:56:03.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:03.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:03.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:03.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Jan 20 20:56:03.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:03.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:03.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:03.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:03.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:03.069: INFO:
Jan 20 20:56:05.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:05.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:05.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:05.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Jan 20 20:56:05.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:05.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:05.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:05.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:05.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:05.076: INFO:
Jan 20 20:56:07.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:07.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:07.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:07.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Jan 20 20:56:07.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:07.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:07.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:07.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:07.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:07.071: INFO:
Jan 20 20:56:09.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:09.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:09.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:09.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Jan 20 20:56:09.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:09.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:09.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:09.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:09.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:09.069: INFO:
Jan 20 20:56:11.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:11.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:11.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:11.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Jan 20 20:56:11.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:11.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:11.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:11.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:11.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:11.071: INFO:
Jan 20 20:56:13.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:13.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:13.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:13.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Jan 20 20:56:13.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:13.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:13.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:13.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:13.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:13.078: INFO:
Jan 20 20:56:15.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:15.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:15.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:15.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Jan 20 20:56:15.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:15.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:15.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:15.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:15.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:15.075: INFO:
Jan 20 20:56:17.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:17.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:17.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:17.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Jan 20 20:56:17.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:17.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:17.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:17.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:17.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:17.068: INFO:
Jan 20 20:56:19.067: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:19.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:19.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:19.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Jan 20 20:56:19.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:19.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:19.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:19.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:19.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:19.068: INFO:
Jan 20 20:56:21.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:21.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:21.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:21.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Jan 20 20:56:21.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:21.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:21.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:21.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:21.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:21.069: INFO:
Jan 20 20:56:23.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:23.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:23.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:23.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Jan 20 20:56:23.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:23.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:23.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:23.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:23.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:23.070: INFO:
Jan 20 20:56:25.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:25.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:25.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:25.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Jan 20 20:56:25.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:25.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:25.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:25.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:25.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:25.069: INFO:
Jan 20 20:56:27.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:27.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:27.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:27.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Jan 20 20:56:27.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:27.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:27.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:27.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:27.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:27.071: INFO:
Jan 20 20:56:29.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:29.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:29.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:29.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Jan 20 20:56:29.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:29.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:29.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:29.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:29.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:29.070: INFO:
Jan 20 20:56:31.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:31.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:31.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:31.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Jan 20 20:56:31.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:31.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:31.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:31.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:31.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:31.072: INFO:
Jan 20 20:56:33.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:33.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:33.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:33.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Jan 20 20:56:33.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:33.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:33.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:33.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:33.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:33.068: INFO:
Jan 20 20:56:35.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:35.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:35.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:35.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Jan 20 20:56:35.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:35.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:35.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:35.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:35.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:35.070: INFO:
Jan 20 20:56:37.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:37.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:37.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:37.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Jan 20 20:56:37.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:37.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:37.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:37.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:37.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:37.072: INFO:
Jan 20 20:56:39.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:39.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:39.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:39.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Jan 20 20:56:39.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:39.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:39.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:39.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:39.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:39.068: INFO:
Jan 20 20:56:41.080: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:41.080: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:41.080: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:41.080: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Jan 20 20:56:41.080: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:41.080: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:41.080: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:41.080: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:41.080: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:41.080: INFO:
Jan 20 20:56:43.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:43.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:43.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:43.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Jan 20 20:56:43.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:43.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:43.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:43.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:43.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:43.069: INFO:
Jan 20 20:56:45.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:45.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:45.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:45.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Jan 20 20:56:45.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:45.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:45.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:45.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:45.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:45.069: INFO:
Jan 20 20:56:47.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:47.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:47.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:47.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Jan 20 20:56:47.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:47.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:47.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:47.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:47.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:47.073: INFO:
Jan 20 20:56:49.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:49.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:49.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:49.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Jan 20 20:56:49.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:49.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:49.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:49.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:49.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:49.075: INFO:
Jan 20 20:56:51.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:51.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:51.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:51.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Jan 20 20:56:51.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:51.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:51.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:51.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:51.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:51.069: INFO:
Jan 20 20:56:53.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:53.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:53.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:53.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Jan 20 20:56:53.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:53.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:53.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:53.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:53.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:53.068: INFO:
Jan 20 20:56:55.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:55.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:55.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:55.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Jan 20 20:56:55.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:55.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:55.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:55.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:55.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:55.071: INFO:
Jan 20 20:56:57.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:57.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:57.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:57.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Jan 20 20:56:57.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:57.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:57.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:57.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:57.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:57.070: INFO:
Jan 20 20:56:59.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:59.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:59.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:56:59.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Jan 20 20:56:59.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:56:59.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:56:59.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:59.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:56:59.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:56:59.071: INFO:
Jan 20 20:57:01.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:01.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:01.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:01.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Jan 20 20:57:01.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:01.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:01.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:01.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:01.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:01.069: INFO:
Jan 20 20:57:03.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:03.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:03.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:03.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Jan 20 20:57:03.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:03.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:03.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:03.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:03.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:03.069: INFO:
Jan 20 20:57:05.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:05.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:05.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:05.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Jan 20 20:57:05.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:05.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:05.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:05.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:05.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:05.070: INFO:
Jan 20 20:57:07.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:07.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:07.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:07.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Jan 20 20:57:07.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:07.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:07.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:07.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:07.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:07.077: INFO:
Jan 20 20:57:09.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:09.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:09.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:09.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Jan 20 20:57:09.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:09.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:09.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:09.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:09.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:09.075: INFO:
Jan 20 20:57:11.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:11.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:11.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:11.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Jan 20 20:57:11.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:11.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:11.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:11.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:11.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:11.068: INFO:
Jan 20 20:57:13.081: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:13.081: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:13.081: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:13.081: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Jan 20 20:57:13.081: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:13.081: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:13.081: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:13.081: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:13.081: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:13.081: INFO:
Jan 20 20:57:15.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:15.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:15.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:15.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Jan 20 20:57:15.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:15.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:15.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:15.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:15.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:15.070: INFO:
Jan 20 20:57:17.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:17.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:17.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:17.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Jan 20 20:57:17.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:17.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:17.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:17.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:17.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:17.070: INFO:
Jan 20 20:57:19.067: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:19.067: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:19.067: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:19.067: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Jan 20 20:57:19.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:19.067: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:19.067: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:19.067: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:19.067: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:19.067: INFO:
Jan 20 20:57:21.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:21.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:21.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:21.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Jan 20 20:57:21.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:21.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:21.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:21.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:21.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:21.068: INFO:
Jan 20 20:57:23.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:23.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:23.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:23.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Jan 20 20:57:23.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:23.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:23.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:23.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:23.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:23.070: INFO:
Jan 20 20:57:25.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:25.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:25.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:25.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Jan 20 20:57:25.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:25.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:25.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:25.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:25.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:25.071: INFO:
Jan 20 20:57:27.079: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:27.079: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:27.079: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:27.079: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Jan 20 20:57:27.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:27.079: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:27.079: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:27.079: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:27.079: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:27.079: INFO:
Jan 20 20:57:29.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:29.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:29.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:29.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Jan 20 20:57:29.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:29.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:29.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:29.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:29.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:29.070: INFO:
Jan 20 20:57:31.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:31.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:31.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:31.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Jan 20 20:57:31.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:31.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:31.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:31.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:31.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:31.069: INFO:
Jan 20 20:57:33.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:33.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:33.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:33.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Jan 20 20:57:33.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:33.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:33.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:33.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:33.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:33.068: INFO:
Jan 20 20:57:35.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:35.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:35.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:35.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Jan 20 20:57:35.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:35.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:35.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:35.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:35.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:35.071: INFO:
Jan 20 20:57:37.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:37.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:37.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:37.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Jan 20 20:57:37.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:37.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:37.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:37.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:37.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:37.068: INFO:
Jan 20 20:57:39.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:39.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:39.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:39.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Jan 20 20:57:39.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:39.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:39.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:39.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:39.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:39.069: INFO:
Jan 20 20:57:41.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:41.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:41.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:41.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Jan 20 20:57:41.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:41.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:41.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:41.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:41.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:41.069: INFO:
Jan 20 20:57:43.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:43.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:43.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:43.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Jan 20 20:57:43.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:43.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:43.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:43.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:43.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:43.076: INFO:
Jan 20 20:57:45.067: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:45.067: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:45.067: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:45.067: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Jan 20 20:57:45.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:45.067: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:45.067: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:45.067: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:45.067: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:45.067: INFO:
Jan 20 20:57:47.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:47.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:47.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:47.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Jan 20 20:57:47.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:47.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:47.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:47.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:47.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:47.069: INFO:
Jan 20 20:57:49.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:49.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:49.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:49.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Jan 20 20:57:49.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:49.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:49.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:49.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:49.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:49.069: INFO:
Jan 20 20:57:51.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:51.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:51.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:51.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Jan 20 20:57:51.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:51.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:51.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:51.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:51.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:51.070: INFO:
Jan 20 20:57:53.067: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:53.067: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:53.067: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:53.067: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Jan 20 20:57:53.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:53.067: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:53.067: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:53.067: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:53.067: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:53.067: INFO:
Jan 20 20:57:55.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:55.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:55.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:55.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Jan 20 20:57:55.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:55.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:55.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:55.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:55.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:55.069: INFO:
Jan 20 20:57:57.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:57.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:57.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:57.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Jan 20 20:57:57.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:57.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:57.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:57.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:57.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:57.069: INFO:
Jan 20 20:57:59.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:59.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:59.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:57:59.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Jan 20 20:57:59.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:57:59.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:57:59.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:59.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:57:59.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:57:59.077: INFO:
Jan 20 20:58:01.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:01.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:01.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:01.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Jan 20 20:58:01.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:01.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:01.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:01.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:01.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:01.070: INFO:
Jan 20 20:58:03.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:03.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:03.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:03.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Jan 20 20:58:03.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:03.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:03.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:03.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:03.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:03.075: INFO:
Jan 20 20:58:05.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:05.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:05.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:05.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Jan 20 20:58:05.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:05.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:05.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:05.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:05.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:05.071: INFO:
Jan 20 20:58:07.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:07.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:07.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:07.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Jan 20 20:58:07.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:07.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:07.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:07.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:07.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:07.068: INFO:
Jan 20 20:58:09.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:09.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:09.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:09.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Jan 20 20:58:09.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:09.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:09.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:09.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:09.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:09.070: INFO:
Jan 20 20:58:11.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:11.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:11.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:11.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Jan 20 20:58:11.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:11.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:11.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:11.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:11.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:11.068: INFO:
Jan 20 20:58:13.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:13.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:13.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:13.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Jan 20 20:58:13.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:13.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:13.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:13.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:13.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:13.077: INFO:
Jan 20 20:58:15.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:15.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:15.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:15.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Jan 20 20:58:15.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:15.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:15.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:15.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:15.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:15.074: INFO:
Jan 20 20:58:17.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:17.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:17.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:17.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Jan 20 20:58:17.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:17.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:17.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:17.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:17.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:17.068: INFO:
Jan 20 20:58:19.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:19.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:19.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:19.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Jan 20 20:58:19.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:19.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:19.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:19.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:19.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:19.069: INFO:
Jan 20 20:58:21.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:21.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:21.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:21.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Jan 20 20:58:21.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:21.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:21.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:21.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:21.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:21.070: INFO:
Jan 20 20:58:23.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:23.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:23.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:23.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Jan 20 20:58:23.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:23.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:23.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:23.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:23.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:23.069: INFO:
Jan 20 20:58:25.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:25.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:25.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:25.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Jan 20 20:58:25.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:25.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:25.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:25.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:25.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:25.070: INFO:
Jan 20 20:58:27.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:27.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:27.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:27.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Jan 20 20:58:27.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:27.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:27.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:27.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:27.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:27.070: INFO:
Jan 20 20:58:29.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:29.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:29.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:29.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Jan 20 20:58:29.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:29.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:29.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:29.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:29.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:29.068: INFO:
Jan 20 20:58:31.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:31.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:31.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:31.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Jan 20 20:58:31.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:31.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:31.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:31.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:31.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:31.070: INFO:
Jan 20 20:58:33.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:33.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:33.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:33.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Jan 20 20:58:33.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:33.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:33.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:33.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:33.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:33.070: INFO:
Jan 20 20:58:35.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:35.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:35.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:35.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Jan 20 20:58:35.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:35.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:35.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:35.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:35.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:35.071: INFO:
Jan 20 20:58:37.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:37.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:37.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:37.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Jan 20 20:58:37.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:37.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:37.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:37.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:37.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:37.069: INFO:
Jan 20 20:58:39.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:39.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:39.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:39.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Jan 20 20:58:39.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:39.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:39.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:39.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:39.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:39.070: INFO:
Jan 20 20:58:41.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:41.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:41.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:41.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Jan 20 20:58:41.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:41.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:41.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:41.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:41.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:41.071: INFO:
Jan 20 20:58:43.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:43.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:43.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:43.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Jan 20 20:58:43.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:43.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:43.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:43.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:43.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:43.068: INFO:
Jan 20 20:58:45.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:45.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:45.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:45.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Jan 20 20:58:45.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:45.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:45.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:45.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:45.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:45.069: INFO:
Jan 20 20:58:47.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:47.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:47.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:47.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Jan 20 20:58:47.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:47.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:47.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:47.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:47.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:47.068: INFO:
Jan 20 20:58:49.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:49.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:49.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:49.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Jan 20 20:58:49.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:49.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:49.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:49.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:49.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:49.068: INFO:
Jan 20 20:58:51.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:51.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:51.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:51.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Jan 20 20:58:51.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:51.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:51.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:51.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:51.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:51.069: INFO:
Jan 20 20:58:53.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:53.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:53.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:53.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Jan 20 20:58:53.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:53.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:53.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:53.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:53.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:53.069: INFO:
Jan 20 20:58:55.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:55.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:55.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:55.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Jan 20 20:58:55.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:55.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:55.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:55.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:55.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:55.072: INFO:
Jan 20 20:58:57.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:57.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:57.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:57.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Jan 20 20:58:57.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:57.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:57.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:57.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:57.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:57.071: INFO:
Jan 20 20:58:59.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:59.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:59.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:58:59.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Jan 20 20:58:59.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:58:59.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:58:59.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:59.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:58:59.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:58:59.070: INFO:
Jan 20 20:59:01.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:01.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:01.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:01.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Jan 20 20:59:01.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:01.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:01.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:01.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:01.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:01.068: INFO:
Jan 20 20:59:03.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:03.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:03.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:03.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Jan 20 20:59:03.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:03.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:03.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:03.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:03.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:03.069: INFO:
Jan 20 20:59:05.083: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:05.083: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:05.083: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:05.083: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Jan 20 20:59:05.083: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:05.083: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:05.083: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:05.083: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:05.083: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:05.083: INFO:
Jan 20 20:59:07.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:07.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:07.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:07.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Jan 20 20:59:07.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:07.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:07.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:07.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:07.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:07.070: INFO:
Jan 20 20:59:09.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:09.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:09.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:09.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Jan 20 20:59:09.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:09.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:09.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:09.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:09.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:09.072: INFO:
Jan 20 20:59:11.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:11.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:11.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:11.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Jan 20 20:59:11.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:11.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:11.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:11.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:11.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:11.069: INFO:
Jan 20 20:59:13.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:13.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:13.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:13.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Jan 20 20:59:13.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:13.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:13.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:13.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:13.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:13.070: INFO:
Jan 20 20:59:15.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:15.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:15.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:15.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Jan 20 20:59:15.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:15.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:15.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:15.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:15.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:15.070: INFO:
Jan 20 20:59:17.068: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:17.068: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:17.068: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:17.068: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Jan 20 20:59:17.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:17.068: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:17.068: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:17.068: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:17.068: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:17.068: INFO:
Jan 20 20:59:19.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:19.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:19.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:19.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Jan 20 20:59:19.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:19.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:19.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:19.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:19.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:19.071: INFO:
Jan 20 20:59:21.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:21.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:21.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:21.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Jan 20 20:59:21.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:21.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:21.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:21.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:21.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:21.069: INFO:
Jan 20 20:59:23.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:23.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:23.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:23.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Jan 20 20:59:23.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:23.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:23.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:23.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:23.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:23.073: INFO:
Jan 20 20:59:25.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:25.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:25.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:25.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Jan 20 20:59:25.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:25.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:25.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:25.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:25.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:25.071: INFO:
Jan 20 20:59:27.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:27.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:27.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:27.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Jan 20 20:59:27.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:27.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:27.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:27.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:27.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:27.070: INFO:
Jan 20 20:59:29.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:29.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:29.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:29.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Jan 20 20:59:29.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:29.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:29.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:29.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:29.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:29.071: INFO:
Jan 20 20:59:31.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:31.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:31.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:31.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Jan 20 20:59:31.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:31.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:31.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:31.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:31.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:31.070: INFO:
Jan 20 20:59:33.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:33.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:33.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:33.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Jan 20 20:59:33.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:33.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:33.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:33.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:33.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:33.069: INFO:
Jan 20 20:59:35.069: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:35.069: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:35.069: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:35.069: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Jan 20 20:59:35.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:35.069: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:35.069: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:35.069: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:35.069: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:35.069: INFO:
Jan 20 20:59:37.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:37.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:37.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:37.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Jan 20 20:59:37.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:37.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:37.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:37.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:37.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:37.071: INFO:
Jan 20 20:59:39.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:39.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:39.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:39.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Jan 20 20:59:39.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:39.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:39.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:39.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:39.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:39.076: INFO:
Jan 20 20:59:41.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:41.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:41.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:41.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Jan 20 20:59:41.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:41.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:41.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:41.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:41.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:41.074: INFO:
Jan 20 20:59:43.079: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:43.079: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:43.079: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:43.079: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Jan 20 20:59:43.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:43.079: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:43.079: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:43.079: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:43.079: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:43.079: INFO:
Jan 20 20:59:45.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:45.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:45.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:45.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Jan 20 20:59:45.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:45.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:45.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:45.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:45.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:45.074: INFO:
Jan 20 20:59:47.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:47.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:47.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:47.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Jan 20 20:59:47.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:47.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:47.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:47.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:47.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:47.077: INFO:
Jan 20 20:59:49.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:49.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:49.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:49.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Jan 20 20:59:49.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:49.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:49.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:49.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:49.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:49.078: INFO:
Jan 20 20:59:51.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:51.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:51.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:51.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Jan 20 20:59:51.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:51.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:51.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:51.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:51.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:51.074: INFO:
Jan 20 20:59:53.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:53.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:53.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:53.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Jan 20 20:59:53.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:53.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:53.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:53.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:53.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:53.073: INFO:
Jan 20 20:59:55.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:55.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:55.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:55.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Jan 20 20:59:55.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:55.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:55.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:55.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:55.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:55.078: INFO:
Jan 20 20:59:57.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:57.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:57.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:57.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Jan 20 20:59:57.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:57.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:57.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:57.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:57.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:57.075: INFO:
Jan 20 20:59:59.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:59.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:59.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 20:59:59.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Jan 20 20:59:59.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 20:59:59.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 20:59:59.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:59.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 20:59:59.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 20:59:59.077: INFO:
Jan 20 21:00:01.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:01.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:01.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:01.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Jan 20 21:00:01.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:01.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:01.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:01.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:01.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:01.073: INFO:
Jan 20 21:00:03.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:03.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:03.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:03.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Jan 20 21:00:03.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:03.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:03.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:03.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:03.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:03.075: INFO:
Jan 20 21:00:05.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:05.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:05.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:05.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Jan 20 21:00:05.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:05.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:05.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:05.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:05.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:05.075: INFO:
Jan 20 21:00:07.083: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:07.083: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:07.083: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:07.083: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Jan 20 21:00:07.083: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:07.083: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:07.083: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:07.083: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:07.083: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:07.083: INFO:
Jan 20 21:00:09.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:09.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:09.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:09.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Jan 20 21:00:09.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:09.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:09.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:09.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:09.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:09.073: INFO:
Jan 20 21:00:11.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:11.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:11.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:11.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Jan 20 21:00:11.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:11.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:11.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:11.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:11.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:11.076: INFO:
Jan 20 21:00:13.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:13.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:13.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:13.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Jan 20 21:00:13.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:13.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:13.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:13.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:13.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:13.073: INFO:
Jan 20 21:00:15.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:15.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:15.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:15.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Jan 20 21:00:15.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:15.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:15.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:15.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:15.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:15.073: INFO:
Jan 20 21:00:17.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:17.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:17.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:17.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Jan 20 21:00:17.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:17.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:17.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:17.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:17.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:17.073: INFO:
Jan 20 21:00:19.087: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:19.087: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:19.087: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:19.087: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Jan 20 21:00:19.087: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:19.087: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:19.087: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:19.088: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:19.088: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:19.088: INFO:
Jan 20 21:00:21.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:21.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:21.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:21.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Jan 20 21:00:21.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:21.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:21.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:21.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:21.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:21.075: INFO:
Jan 20 21:00:23.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:23.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:23.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:23.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Jan 20 21:00:23.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:23.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:23.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:23.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:23.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:23.075: INFO:
Jan 20 21:00:25.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:25.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:25.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:25.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Jan 20 21:00:25.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:25.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:25.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:25.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:25.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:25.076: INFO:
Jan 20 21:00:27.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:27.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:27.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:27.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Jan 20 21:00:27.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:27.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:27.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:27.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:27.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:27.074: INFO:
Jan 20 21:00:29.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:29.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:29.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:29.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Jan 20 21:00:29.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:29.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:29.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:29.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:29.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:29.076: INFO:
Jan 20 21:00:31.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:31.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:31.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:31.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Jan 20 21:00:31.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:31.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:31.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:31.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:31.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:31.073: INFO:
Jan 20 21:00:33.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:33.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:33.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:33.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Jan 20 21:00:33.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:33.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:33.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:33.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:33.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:33.077: INFO:
Jan 20 21:00:35.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:35.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:35.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:35.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Jan 20 21:00:35.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:35.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:35.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:35.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:35.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:35.076: INFO:
Jan 20 21:00:37.083: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:37.083: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:37.083: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:37.083: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Jan 20 21:00:37.083: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:37.083: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:37.083: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:37.083: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:37.083: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:37.083: INFO:
Jan 20 21:00:39.083: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:39.083: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:39.083: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:39.083: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Jan 20 21:00:39.083: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:39.083: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:39.083: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:39.083: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:39.083: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:39.083: INFO:
Jan 20 21:00:41.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:41.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:41.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:41.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Jan 20 21:00:41.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:41.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:41.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:41.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:41.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:41.074: INFO:
Jan 20 21:00:43.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:43.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:43.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:43.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Jan 20 21:00:43.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:43.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:43.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:43.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:43.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:43.078: INFO:
Jan 20 21:00:45.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:45.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:45.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:45.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Jan 20 21:00:45.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:45.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:45.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:45.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:45.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:45.073: INFO:
Jan 20 21:00:47.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:47.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:47.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:47.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Jan 20 21:00:47.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:47.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:47.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:47.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:47.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:47.074: INFO:
Jan 20 21:00:49.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:49.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:49.079: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:49.079: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Jan 20 21:00:49.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:49.079: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:49.079: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:49.079: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:49.079: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:49.079: INFO:
Jan 20 21:00:51.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:51.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:51.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:51.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Jan 20 21:00:51.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:51.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:51.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:51.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:51.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:51.072: INFO:
Jan 20 21:00:53.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:53.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:53.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:53.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Jan 20 21:00:53.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:53.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:53.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:53.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:53.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:53.075: INFO:
Jan 20 21:00:55.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:55.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:55.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:55.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Jan 20 21:00:55.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:55.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:55.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:55.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:55.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:55.075: INFO:
Jan 20 21:00:57.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:57.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:57.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:57.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Jan 20 21:00:57.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:57.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:57.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:57.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:57.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:57.075: INFO:
Jan 20 21:00:59.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:59.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:59.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:00:59.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Jan 20 21:00:59.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:00:59.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:00:59.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:59.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:00:59.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:00:59.074: INFO:
Jan 20 21:01:01.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:01.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:01.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:01.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Jan 20 21:01:01.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:01.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:01.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:01.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:01.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:01.078: INFO:
Jan 20 21:01:03.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:03.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:03.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:03.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Jan 20 21:01:03.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:03.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:03.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:03.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:03.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:03.072: INFO:
Jan 20 21:01:05.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:05.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:05.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:05.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Jan 20 21:01:05.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:05.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:05.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:05.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:05.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:05.074: INFO:
Jan 20 21:01:07.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:07.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:07.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:07.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Jan 20 21:01:07.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:07.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:07.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:07.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:07.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:07.072: INFO:
Jan 20 21:01:09.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:09.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:09.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:09.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Jan 20 21:01:09.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:09.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:09.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:09.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:09.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:09.072: INFO:
Jan 20 21:01:11.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:11.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:11.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:11.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Jan 20 21:01:11.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:11.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:11.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:11.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:11.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:11.075: INFO:
Jan 20 21:01:13.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:13.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:13.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:13.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Jan 20 21:01:13.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:13.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:13.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:13.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:13.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:13.075: INFO:
Jan 20 21:01:15.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:15.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:15.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:15.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Jan 20 21:01:15.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:15.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:15.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:15.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:15.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:15.076: INFO:
Jan 20 21:01:17.078: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:17.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:17.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:17.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Jan 20 21:01:17.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:17.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:17.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:17.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:17.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:17.078: INFO:
Jan 20 21:01:19.080: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:19.080: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:19.080: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:19.080: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Jan 20 21:01:19.080: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:19.080: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:19.080: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:19.080: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:19.080: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:19.081: INFO:
Jan 20 21:01:21.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:21.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:21.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:21.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Jan 20 21:01:21.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:21.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:21.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:21.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:21.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:21.075: INFO:
Jan 20 21:01:23.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:23.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:23.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:23.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Jan 20 21:01:23.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:23.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:23.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:23.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:23.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:23.071: INFO:
Jan 20 21:01:25.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:25.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:25.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:25.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Jan 20 21:01:25.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:25.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:25.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:25.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:25.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:25.073: INFO:
Jan 20 21:01:27.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:27.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:27.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:27.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Jan 20 21:01:27.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:27.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:27.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:27.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:27.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:27.075: INFO:
Jan 20 21:01:29.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:29.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:29.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:29.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Jan 20 21:01:29.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:29.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:29.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:29.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:29.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:29.076: INFO:
Jan 20 21:01:31.080: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:31.081: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:31.081: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:31.081: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Jan 20 21:01:31.081: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:31.081: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:31.081: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:31.081: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:31.081: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:31.081: INFO:
Jan 20 21:01:33.096: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:33.096: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:33.096: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:33.096: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Jan 20 21:01:33.096: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:33.096: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:33.096: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:33.096: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:33.096: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:33.096: INFO:
Jan 20 21:01:35.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:35.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:35.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:35.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Jan 20 21:01:35.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:35.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:35.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:35.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:35.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:35.076: INFO:
Jan 20 21:01:37.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:37.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:37.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:37.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Jan 20 21:01:37.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:37.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:37.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:37.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:37.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:37.074: INFO:
Jan 20 21:01:39.079: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:39.079: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:39.079: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:39.079: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Jan 20 21:01:39.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:39.079: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:39.079: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:39.079: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:39.079: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:39.079: INFO:
Jan 20 21:01:41.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:41.078: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:41.078: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:41.078: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Jan 20 21:01:41.078: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:41.078: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:41.078: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:41.078: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:41.078: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:41.078: INFO:
Jan 20 21:01:43.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:43.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:43.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:43.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Jan 20 21:01:43.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:43.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:43.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:43.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:43.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:43.077: INFO:
Jan 20 21:01:45.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:45.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:45.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:45.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Jan 20 21:01:45.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:45.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:45.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:45.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:45.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:45.076: INFO:
Jan 20 21:01:47.083: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:47.083: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:47.083: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:47.083: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Jan 20 21:01:47.083: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:47.083: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:47.083: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:47.083: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:47.083: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:47.083: INFO:
Jan 20 21:01:49.080: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:49.080: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:49.080: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:49.080: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Jan 20 21:01:49.080: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:49.080: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:49.080: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:49.080: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:49.080: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:49.080: INFO:
Jan 20 21:01:51.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:51.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:51.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:51.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Jan 20 21:01:51.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:51.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:51.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:51.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:51.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:51.075: INFO:
Jan 20 21:01:53.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:53.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:53.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:53.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Jan 20 21:01:53.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:53.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:53.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:53.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:53.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:53.075: INFO:
Jan 20 21:01:55.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:55.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:55.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:55.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Jan 20 21:01:55.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:55.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:55.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:55.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:55.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:55.077: INFO:
Jan 20 21:01:57.081: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:57.081: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:57.081: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:57.081: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Jan 20 21:01:57.081: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:57.081: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:57.081: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:57.081: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:57.081: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:57.081: INFO:
Jan 20 21:01:59.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:59.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:59.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:01:59.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Jan 20 21:01:59.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:01:59.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:01:59.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:59.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:01:59.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:01:59.072: INFO:
Jan 20 21:02:01.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:01.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:01.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:01.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Jan 20 21:02:01.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:01.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:01.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:01.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:01.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:01.072: INFO:
Jan 20 21:02:03.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:03.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:03.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:03.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Jan 20 21:02:03.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:03.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:03.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:03.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:03.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:03.073: INFO:
Jan 20 21:02:05.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:05.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:05.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:05.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Jan 20 21:02:05.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:05.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:05.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:05.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:05.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:05.073: INFO:
Jan 20 21:02:07.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:07.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:07.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:07.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Jan 20 21:02:07.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:07.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:07.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:07.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:07.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:07.075: INFO:
Jan 20 21:02:09.081: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:09.081: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:09.081: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:09.081: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Jan 20 21:02:09.081: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:09.081: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:09.081: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:09.081: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:09.081: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:09.081: INFO:
Jan 20 21:02:11.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:11.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:11.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:11.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Jan 20 21:02:11.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:11.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:11.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:11.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:11.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:11.076: INFO:
Jan 20 21:02:13.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:13.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:13.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:13.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Jan 20 21:02:13.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:13.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:13.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:13.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:13.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:13.072: INFO:
Jan 20 21:02:15.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:15.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:15.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:15.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Jan 20 21:02:15.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:15.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:15.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:15.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:15.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:15.076: INFO:
Jan 20 21:02:17.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:17.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:17.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:17.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Jan 20 21:02:17.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:17.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:17.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:17.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:17.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:17.073: INFO:
Jan 20 21:02:19.079: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:19.079: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:19.079: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:19.079: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Jan 20 21:02:19.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:19.079: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:19.079: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:19.079: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:19.079: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:19.079: INFO:
Jan 20 21:02:21.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:21.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:21.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:21.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Jan 20 21:02:21.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:21.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:21.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:21.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:21.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:21.074: INFO:
Jan 20 21:02:23.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:23.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:23.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:23.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Jan 20 21:02:23.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:23.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:23.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:23.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:23.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:23.073: INFO:
Jan 20 21:02:25.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:25.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:25.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:25.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Jan 20 21:02:25.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:25.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:25.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:25.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:25.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:25.071: INFO:
Jan 20 21:02:27.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:27.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:27.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:27.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Jan 20 21:02:27.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:27.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:27.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:27.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:27.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:27.072: INFO:
Jan 20 21:02:29.079: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:29.079: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:29.079: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:29.079: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Jan 20 21:02:29.079: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:29.079: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:29.079: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:29.079: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:29.079: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:29.079: INFO:
Jan 20 21:02:31.080: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:31.080: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:31.080: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:31.080: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Jan 20 21:02:31.080: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:31.080: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:31.080: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:31.080: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:31.080: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:31.080: INFO:
Jan 20 21:02:33.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:33.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:33.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:33.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Jan 20 21:02:33.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:33.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:33.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:33.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:33.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:33.072: INFO:
Jan 20 21:02:35.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:35.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:35.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:35.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Jan 20 21:02:35.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:35.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:35.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:35.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:35.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:35.073: INFO:
Jan 20 21:02:37.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:37.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:37.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:37.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Jan 20 21:02:37.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:37.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:37.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:37.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:37.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:37.071: INFO:
Jan 20 21:02:39.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:39.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:39.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:39.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Jan 20 21:02:39.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:39.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:39.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:39.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:39.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:39.072: INFO:
Jan 20 21:02:41.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:41.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:41.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:41.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Jan 20 21:02:41.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:41.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:41.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:41.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:41.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:41.073: INFO:
Jan 20 21:02:43.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:43.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:43.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:43.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Jan 20 21:02:43.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:43.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:43.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:43.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:43.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:43.074: INFO:
Jan 20 21:02:45.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:45.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:45.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:45.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Jan 20 21:02:45.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:45.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:45.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:45.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:45.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:45.072: INFO:
Jan 20 21:02:47.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:47.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:47.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:47.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Jan 20 21:02:47.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:47.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:47.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:47.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:47.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:47.076: INFO:
Jan 20 21:02:49.077: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:49.077: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:49.077: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:49.077: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Jan 20 21:02:49.077: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:49.077: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:49.077: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:49.077: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:49.077: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:49.077: INFO:
Jan 20 21:02:51.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:51.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:51.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:51.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Jan 20 21:02:51.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:51.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:51.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:51.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:51.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:51.072: INFO:
Jan 20 21:02:53.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:53.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:53.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:53.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Jan 20 21:02:53.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:53.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:53.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:53.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:53.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:53.074: INFO:
Jan 20 21:02:55.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:55.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:55.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:55.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Jan 20 21:02:55.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:55.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:55.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:55.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:55.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:55.075: INFO:
Jan 20 21:02:57.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:57.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:57.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:57.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Jan 20 21:02:57.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:57.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:57.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:57.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:57.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:57.071: INFO:
Jan 20 21:02:59.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:59.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:59.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:02:59.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Jan 20 21:02:59.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:02:59.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:02:59.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:59.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:02:59.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:02:59.076: INFO:
Jan 20 21:03:01.072: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:01.072: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:01.072: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:01.072: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Jan 20 21:03:01.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:01.072: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:01.072: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:01.072: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:01.072: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:01.072: INFO:
Jan 20 21:03:03.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:03.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:03.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:03.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Jan 20 21:03:03.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:03.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:03.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:03.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:03.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:03.076: INFO:
Jan 20 21:03:05.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:05.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:05.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:05.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Jan 20 21:03:05.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:05.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:05.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:05.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:05.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:05.074: INFO:
Jan 20 21:03:07.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:07.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:07.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:07.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Jan 20 21:03:07.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:07.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:07.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:07.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:07.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:07.071: INFO:
Jan 20 21:03:09.075: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:09.075: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:09.075: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:09.075: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Jan 20 21:03:09.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:09.075: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:09.075: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:09.075: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:09.075: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:09.075: INFO:
Jan 20 21:03:11.071: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:11.071: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:11.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:11.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Jan 20 21:03:11.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:11.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:11.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:11.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:11.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:11.071: INFO:
Jan 20 21:03:13.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:13.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:13.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:13.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Jan 20 21:03:13.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:13.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:13.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:13.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:13.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:13.070: INFO:
Jan 20 21:03:15.082: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:15.082: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:15.082: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:15.082: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Jan 20 21:03:15.082: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:15.082: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:15.082: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:15.082: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:15.082: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:15.082: INFO:
Jan 20 21:03:17.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:17.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:17.070: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:17.070: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Jan 20 21:03:17.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:17.070: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:17.070: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:17.070: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:17.070: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:17.070: INFO:
Jan 20 21:03:19.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:19.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:19.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:19.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Jan 20 21:03:19.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:19.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:19.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:19.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:19.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:19.076: INFO:
Jan 20 21:03:21.080: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:21.080: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:21.080: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:21.080: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Jan 20 21:03:21.080: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:21.080: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:21.080: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:21.080: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:21.080: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:21.080: INFO:
Jan 20 21:03:23.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:23.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:23.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:23.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Jan 20 21:03:23.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:23.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:23.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:23.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:23.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:23.074: INFO:
Jan 20 21:03:25.073: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:25.073: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:25.073: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:25.073: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Jan 20 21:03:25.073: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:25.073: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:25.073: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:25.073: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:25.073: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:25.073: INFO:
Jan 20 21:03:27.074: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:27.074: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:27.074: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:27.074: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Jan 20 21:03:27.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:27.074: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:27.074: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:27.074: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:27.074: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:27.074: INFO:
Jan 20 21:03:29.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:29.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:29.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:29.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Jan 20 21:03:29.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:29.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:29.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:29.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:29.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:29.076: INFO:
Jan 20 21:03:31.076: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:31.076: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:31.076: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:31.076: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Jan 20 21:03:31.076: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:31.076: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:31.076: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:31.076: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:31.076: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:31.076: INFO:
Jan 20 21:03:33.070: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:33.070: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:33.071: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:33.071: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Jan 20 21:03:33.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:33.071: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:33.071: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:33.071: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:33.071: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:33.071: INFO:
Jan 20 21:03:35.090: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:35.090: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:35.090: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:35.090: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 20 21:03:35.090: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:35.090: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:35.090: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:35.090: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:35.090: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:35.090: INFO:
Jan 20 21:03:35.219: INFO: The status of Pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:35.219: INFO: The status of Pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:35.219: INFO: The status of Pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 20 21:03:35.219: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 20 21:03:35.219: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 20 21:03:35.219: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:35.219: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:35.219: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:35.219: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:35.219: INFO:
STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/20/23 21:03:35.219
STEP: Found 95 events. - test/e2e/framework/debug/dump.go:46 @ 01/20/23 21:03:35.275
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:32 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-4dba30-control-plane-79kmh_051f048e-8109-4436-b5cb-68728f7c4ad9 became leader
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:32 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-4dba30-control-plane-79kmh_7afed16a-3136-4eda-838d-052c682466e0 became leader
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-gqqzk
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-jw4sc
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for coredns-56f4c55bf9-gqqzk: {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..
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for coredns-56f4c55bf9-jw4sc: {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..
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-5chhb
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:37 +0000 UTC - event for kube-proxy-5chhb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-5chhb to capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:38 +0000 UTC - event for kube-proxy-5chhb: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:40 +0000 UTC - event for kube-proxy-5chhb: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container kube-proxy
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:40 +0000 UTC - event for kube-proxy-5chhb: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094" in 2.355971s (2.355978501s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:50:40 +0000 UTC - event for kube-proxy-5chhb: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container kube-proxy
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:00 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:00 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-8fkpt
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:00 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {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..
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:02 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:02 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-fthjx
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:02 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {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..
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:02 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-7b764
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:02 +0000 UTC - event for calico-node-7b764: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-7b764 to capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:02 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:10 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.628040079s (7.628047979s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:10 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container upgrade-ipam
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:10 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container upgrade-ipam
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:13 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container install-cni
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:13 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:13 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container install-cni
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-fthjx to capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {kubelet capz-conf-4dba30-control-plane-79kmh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ce1532d9f499da66ef1f6c2474302e04b92cf583eb982aa72e66a3eae16d453a": 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/
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for coredns-56f4c55bf9-gqqzk: {kubelet capz-conf-4dba30-control-plane-79kmh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "304d6f192e4a962edd050181e38fa51d8d07b90809f4f97496c7b9e901544dcc": 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/
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for coredns-56f4c55bf9-gqqzk: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-gqqzk to capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for coredns-56f4c55bf9-jw4sc: {kubelet capz-conf-4dba30-control-plane-79kmh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "1cf1c27f740a28b4589640ca5df8e0e84bf4dad71b01d8295ac005babe375b9d": 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/
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for coredns-56f4c55bf9-jw4sc: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-jw4sc to capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {kubelet capz-conf-4dba30-control-plane-79kmh} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "81df3a05df8655665050a619a88cb3e4cd92ccc4dec906ef686f2fd424c501ea": 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/
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:16 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-8fkpt to capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:24 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 8.379385692s (8.379398693s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:24 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container calico-node
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:24 +0000 UTC - event for calico-node-7b764: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container calico-node
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:27 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:30 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:33 +0000 UTC - event for coredns-56f4c55bf9-gqqzk: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:33 +0000 UTC - event for coredns-56f4c55bf9-gqqzk: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container coredns
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:33 +0000 UTC - event for coredns-56f4c55bf9-jw4sc: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:33 +0000 UTC - event for coredns-56f4c55bf9-jw4sc: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container coredns
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:33 +0000 UTC - event for coredns-56f4c55bf9-jw4sc: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container coredns
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:34 +0000 UTC - event for coredns-56f4c55bf9-gqqzk: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container coredns
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:34 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container metrics-server
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:34 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container metrics-server
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:34 +0000 UTC - event for metrics-server-c9574f845-8fkpt: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 7.011932015s (7.012166218s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:40 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {kubelet capz-conf-4dba30-control-plane-79kmh} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 6.07178671s (10.658577023s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:40 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {kubelet capz-conf-4dba30-control-plane-79kmh} Created: Created container calico-kube-controllers
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:51:40 +0000 UTC - event for calico-kube-controllers-657b584867-fthjx: {kubelet capz-conf-4dba30-control-plane-79kmh} Started: Started container calico-kube-controllers
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:42 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-gv98t
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:42 +0000 UTC - event for calico-node-gv98t: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-gv98t to capz-conf-4dba30-md-0-kbtgj
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:42 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-h6r5m
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:42 +0000 UTC - event for kube-proxy-h6r5m: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-h6r5m to capz-conf-4dba30-md-0-kbtgj
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:46 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-qzczz
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:46 +0000 UTC - event for calico-node-qzczz: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-qzczz to capz-conf-4dba30-md-0-jzskz
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:46 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-q9c5b
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:46 +0000 UTC - event for kube-proxy-q9c5b: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-q9c5b to capz-conf-4dba30-md-0-jzskz
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:50 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:50 +0000 UTC - event for kube-proxy-h6r5m: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:57 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.758929531s (6.759055439s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:57 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Created: Created container upgrade-ipam
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:57 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Started: Started container upgrade-ipam
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:57 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:52:57 +0000 UTC - event for kube-proxy-q9c5b: {kubelet capz-conf-4dba30-md-0-jzskz} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:00 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:00 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Created: Created container install-cni
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:00 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Started: Started container install-cni
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:01 +0000 UTC - event for kube-proxy-h6r5m: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094" in 4.253346635s (11.007312768s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:02 +0000 UTC - event for kube-proxy-h6r5m: {kubelet capz-conf-4dba30-md-0-kbtgj} Created: Created container kube-proxy
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:02 +0000 UTC - event for kube-proxy-h6r5m: {kubelet capz-conf-4dba30-md-0-kbtgj} Started: Started container kube-proxy
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:03 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.445390879s (6.445485284s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:03 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Created: Created container upgrade-ipam
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:04 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:04 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Started: Started container upgrade-ipam
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:06 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:06 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Created: Created container install-cni
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:06 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Started: Started container install-cni
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:08 +0000 UTC - event for kube-proxy-q9c5b: {kubelet capz-conf-4dba30-md-0-jzskz} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094" in 4.620512961s (11.063792613s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:08 +0000 UTC - event for kube-proxy-q9c5b: {kubelet capz-conf-4dba30-md-0-jzskz} Created: Created container kube-proxy
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:09 +0000 UTC - event for kube-proxy-q9c5b: {kubelet capz-conf-4dba30-md-0-jzskz} Started: Started container kube-proxy
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:11 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:12 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} 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
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:12 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Started: Started container calico-node
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:12 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Created: Created container calico-node
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:12 +0000 UTC - event for calico-node-gv98t: {kubelet capz-conf-4dba30-md-0-kbtgj} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.583905088s (7.583922988s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:18 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.186425357s (7.186432057s including waiting)
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:18 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Created: Created container calico-node
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:18 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Started: Started container calico-node
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:19 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} 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
Jan 20 21:03:35.275: INFO: At 2023-01-20 20:53:20 +0000 UTC - event for calico-node-qzczz: {kubelet capz-conf-4dba30-md-0-jzskz} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503
Jan 20 21:03:35.333: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 20 21:03:35.333: INFO: calico-kube-controllers-657b584867-fthjx capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC }]
Jan 20 21:03:35.333: INFO: calico-node-7b764 capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:33 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:02 +0000 UTC }]
Jan 20 21:03:35.333: INFO: calico-node-gv98t capz-conf-4dba30-md-0-kbtgj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:04 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:52:42 +0000 UTC }]
Jan 20 21:03:35.333: INFO: calico-node-qzczz capz-conf-4dba30-md-0-jzskz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:11 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:52:46 +0000 UTC }]
Jan 20 21:03:35.333: INFO: coredns-56f4c55bf9-gqqzk capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:34 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:34 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC }]
Jan 20 21:03:35.333: INFO: coredns-56f4c55bf9-jw4sc capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:34 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:34 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC }]
Jan 20 21:03:35.333: INFO: etcd-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:33 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:43 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:43 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:33 +0000 UTC }]
Jan 20 21:03:35.333: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:35.333: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
Jan 20 21:03:35.333: INFO: kube-proxy-5chhb capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:37 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:37 +0000 UTC }]
Jan 20 21:03:35.333: INFO: kube-proxy-h6r5m capz-conf-4dba30-md-0-kbtgj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:52:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:03 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:52:42 +0000 UTC }]
Jan 20 21:03:35.333: INFO: kube-proxy-q9c5b capz-conf-4dba30-md-0-jzskz Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:52:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:53:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:52:46 +0000 UTC }]
Jan 20 21:03:35.333: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:50:12 +0000 UTC }]
Jan 20 21:03:35.333: INFO: metrics-server-c9574f845-8fkpt capz-conf-4dba30-control-plane-79kmh Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-20 20:51:16 +0000 UTC }]
Jan 20 21:03:35.333: INFO:
Jan 20 21:03:35.606: INFO:
Logging node info for node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.642: INFO: Node Info: &Node{ObjectMeta:{capz-conf-4dba30-control-plane-79kmh 04b13023-7a9f-4fed-bc49-f70f7bf79b1a 1741 0 2023-01-20 20:50:28 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:canadacentral-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-4dba30-control-plane-79kmh kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:canadacentral-1] map[cluster.x-k8s.io/cluster-name:capz-conf-4dba30 cluster.x-k8s.io/cluster-namespace:capz-conf-4dba30 cluster.x-k8s.io/machine:capz-conf-4dba30-control-plane-7vl6t cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-4dba30-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.56.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-20 20:50:27 +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 2023-01-20 20:50:31 +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 2023-01-20 20:50:58 +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 2023-01-20 20:51:15 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-20 20:51:25 +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 2023-01-20 21:02:15 +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-4dba30/providers/Microsoft.Compute/virtualMachines/capz-conf-4dba30-control-plane-79kmh,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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-20 20:51:24 +0000 UTC,LastTransitionTime:2023-01-20 20:51:24 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-20 21:02:15 +0000 UTC,LastTransitionTime:2023-01-20 20:50:11 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-20 21:02:15 +0000 UTC,LastTransitionTime:2023-01-20 20:50:11 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-20 21:02:15 +0000 UTC,LastTransitionTime:2023-01-20 20:50:11 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-20 21:02:15 +0000 UTC,LastTransitionTime:2023-01-20 20:51:15 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-4dba30-control-plane-79kmh,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:8c1563662d3e440aa7f9b518da2938cc,SystemUUID:beffa35f-af14-4643-9cf7-069bcc942fa8,BootID:96fa2bf5-51e1-457f-9654-b979ef096185,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1140+512480e7bac094,KubeProxyVersion:v1.27.0-alpha.0.1140+512480e7bac094,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:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},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:444dbac969c966010ef6b82902e5e327c7fcc86e60371e6d4c01ca17dcd98236 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.1132_b0ed87078e4042],SizeBytes:35455793,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:a3eec2037fdcdccf03316d06c0f4e5f958a81c98bab7a2a7cd94687dce21a139 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.1132_b0ed87078e4042],SizeBytes:32311218,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},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:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:0f957b2ca8a64e02a51c063c433c3daac2649171f59f77524b34d619b3f95189 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094],SizeBytes:21490962,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:8d40760c7c707373ae838394bb298cbd3eee989388929513ee8a338012a9c33e gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.1132_b0ed87078e4042],SizeBytes:21482277,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:858f37df7f3263c56d6add5ce06be3dbacc0a14f3128fbf21be5cbec5505e187 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.1132_b0ed87078e4042],SizeBytes:17468965,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jan 20 21:03:35.642: INFO:
Logging kubelet events for node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.780: INFO:
Logging pods the kubelet thinks is on node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:35.992: INFO: metrics-server-c9574f845-8fkpt started at 2023-01-20 20:51:16 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Container metrics-server ready: true, restart count 0
Jan 20 21:03:35.992: INFO: coredns-56f4c55bf9-jw4sc started at 2023-01-20 20:51:16 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Container coredns ready: true, restart count 0
Jan 20 21:03:35.992: INFO: coredns-56f4c55bf9-gqqzk started at 2023-01-20 20:51:16 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Container coredns ready: true, restart count 0
Jan 20 21:03:35.992: INFO: calico-kube-controllers-657b584867-fthjx started at 2023-01-20 20:51:16 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Container calico-kube-controllers ready: true, restart count 0
Jan 20 21:03:35.992: INFO: kube-controller-manager-capz-conf-4dba30-control-plane-79kmh started at <nil> (0+0 container statuses recorded)
Jan 20 21:03:35.992: INFO: kube-proxy-5chhb started at 2023-01-20 20:50:37 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Container kube-proxy ready: true, restart count 0
Jan 20 21:03:35.992: INFO: calico-node-7b764 started at 2023-01-20 20:51:02 +0000 UTC (2+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 20 21:03:35.992: INFO: Init container install-cni ready: true, restart count 0
Jan 20 21:03:35.992: INFO: Container calico-node ready: true, restart count 0
Jan 20 21:03:35.992: INFO: kube-scheduler-capz-conf-4dba30-control-plane-79kmh started at <nil> (0+0 container statuses recorded)
Jan 20 21:03:35.992: INFO: etcd-capz-conf-4dba30-control-plane-79kmh started at 2023-01-20 20:50:33 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:35.992: INFO: Container etcd ready: true, restart count 0
Jan 20 21:03:35.992: INFO: kube-apiserver-capz-conf-4dba30-control-plane-79kmh started at <nil> (0+0 container statuses recorded)
Jan 20 21:03:36.633: INFO:
Latency metrics for node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:36.633: INFO:
Logging node info for node capz-conf-4dba30-md-0-jzskz
Jan 20 21:03:36.780: INFO: Node Info: &Node{ObjectMeta:{capz-conf-4dba30-md-0-jzskz 28ef181d-1756-468a-9b5e-bbdd88e816fe 1423 0 2023-01-20 20:52:46 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-4dba30-md-0-jzskz kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-4dba30 cluster.x-k8s.io/cluster-namespace:capz-conf-4dba30 cluster.x-k8s.io/machine:capz-conf-4dba30-md-0-6c64997df6-q5qgq cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-4dba30-md-0-6c64997df6 kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.34.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-20 20:52:46 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-20 20:52:46 +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":{}}} } {manager Update v1 2023-01-20 20:52:58 +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 2023-01-20 20:53:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-20 20:53:19 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-20 20:58:43 +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-4dba30/providers/Microsoft.Compute/virtualMachines/capz-conf-4dba30-md-0-jzskz,Unschedulable:false,Taints:[]Taint{},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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-20 20:53:19 +0000 UTC,LastTransitionTime:2023-01-20 20:53:19 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-20 20:58:43 +0000 UTC,LastTransitionTime:2023-01-20 20:52:46 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-20 20:58:43 +0000 UTC,LastTransitionTime:2023-01-20 20:52:46 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-20 20:58:43 +0000 UTC,LastTransitionTime:2023-01-20 20:52:46 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-20 20:58:43 +0000 UTC,LastTransitionTime:2023-01-20 20:53:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-4dba30-md-0-jzskz,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:60cdf32f55ca4563a0cc3b24d6531a1d,SystemUUID:3a4ae206-bc02-dd42-a0f5-09062668481c,BootID:21c00b10-661c-491a-ba20-0806a6d806d2,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1140+512480e7bac094,KubeProxyVersion:v1.27.0-alpha.0.1140+512480e7bac094,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:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:0f957b2ca8a64e02a51c063c433c3daac2649171f59f77524b34d619b3f95189 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094],SizeBytes:21490962,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jan 20 21:03:36.780: INFO:
Logging kubelet events for node capz-conf-4dba30-md-0-jzskz
Jan 20 21:03:36.980: INFO:
Logging pods the kubelet thinks is on node capz-conf-4dba30-md-0-jzskz
Jan 20 21:03:37.191: INFO: calico-node-qzczz started at 2023-01-20 20:52:53 +0000 UTC (2+1 container statuses recorded)
Jan 20 21:03:37.191: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 20 21:03:37.191: INFO: Init container install-cni ready: true, restart count 0
Jan 20 21:03:37.191: INFO: Container calico-node ready: true, restart count 0
Jan 20 21:03:37.191: INFO: kube-proxy-q9c5b started at 2023-01-20 20:52:53 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:37.191: INFO: Container kube-proxy ready: true, restart count 0
Jan 20 21:03:37.814: INFO:
Latency metrics for node capz-conf-4dba30-md-0-jzskz
Jan 20 21:03:37.814: INFO:
Logging node info for node capz-conf-4dba30-md-0-kbtgj
Jan 20 21:03:37.983: INFO: Node Info: &Node{ObjectMeta:{capz-conf-4dba30-md-0-kbtgj 57086300-c4db-4ed1-b4c6-e1b049604888 1418 0 2023-01-20 20:52:42 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-4dba30-md-0-kbtgj kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-4dba30 cluster.x-k8s.io/cluster-namespace:capz-conf-4dba30 cluster.x-k8s.io/machine:capz-conf-4dba30-md-0-6c64997df6-558g8 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-4dba30-md-0-6c64997df6 kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.95.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-20 20:52:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-20 20:52:42 +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":{}}} } {manager Update v1 2023-01-20 20:52:57 +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 2023-01-20 20:53:03 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-20 20:53:13 +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 2023-01-20 20:58:39 +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-4dba30/providers/Microsoft.Compute/virtualMachines/capz-conf-4dba30-md-0-kbtgj,Unschedulable:false,Taints:[]Taint{},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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-20 20:53:12 +0000 UTC,LastTransitionTime:2023-01-20 20:53:12 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-20 20:58:39 +0000 UTC,LastTransitionTime:2023-01-20 20:52:42 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-20 20:58:39 +0000 UTC,LastTransitionTime:2023-01-20 20:52:42 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-20 20:58:39 +0000 UTC,LastTransitionTime:2023-01-20 20:52:42 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-20 20:58:39 +0000 UTC,LastTransitionTime:2023-01-20 20:53:03 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-4dba30-md-0-kbtgj,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:95fb7df710f84ebaa399b8baccd24b3c,SystemUUID:7af63b9b-b9f9-e441-b81b-8349e782aba9,BootID:663c6088-0875-4876-bd65-ca0ea255a597,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1140+512480e7bac094,KubeProxyVersion:v1.27.0-alpha.0.1140+512480e7bac094,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:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:0f957b2ca8a64e02a51c063c433c3daac2649171f59f77524b34d619b3f95189 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1140_512480e7bac094],SizeBytes:21490962,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Jan 20 21:03:37.983: INFO:
Logging kubelet events for node capz-conf-4dba30-md-0-kbtgj
Jan 20 21:03:38.181: INFO:
Logging pods the kubelet thinks is on node capz-conf-4dba30-md-0-kbtgj
Jan 20 21:03:38.386: INFO: calico-node-gv98t started at 2023-01-20 20:52:46 +0000 UTC (2+1 container statuses recorded)
Jan 20 21:03:38.386: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 20 21:03:38.386: INFO: Init container install-cni ready: true, restart count 0
Jan 20 21:03:38.386: INFO: Container calico-node ready: true, restart count 0
Jan 20 21:03:38.386: INFO: kube-proxy-h6r5m started at 2023-01-20 20:52:46 +0000 UTC (0+1 container statuses recorded)
Jan 20 21:03:38.386: INFO: Container kube-proxy ready: true, restart count 0
Jan 20 21:03:39.012: INFO:
Latency metrics for node capz-conf-4dba30-md-0-kbtgj
Jan 20 21:03:39.203: INFO: Running kubectl logs on non-ready containers in kube-system
Jan 20 21:03:39.581: INFO: Failed to get logs of pod kube-apiserver-capz-conf-4dba30-control-plane-79kmh, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-4dba30-control-plane-79kmh)
Jan 20 21:03:39.581: INFO: Logs of kube-system/kube-apiserver-capz-conf-4dba30-control-plane-79kmh:kube-apiserver on node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:39.581: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-4dba30-control-plane-79kmh:kube-apiserver
Jan 20 21:03:39.981: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-4dba30-control-plane-79kmh, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-4dba30-control-plane-79kmh)
Jan 20 21:03:39.981: INFO: Logs of kube-system/kube-controller-manager-capz-conf-4dba30-control-plane-79kmh:kube-controller-manager on node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:39.981: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-4dba30-control-plane-79kmh:kube-controller-manager
Jan 20 21:03:40.380: INFO: Failed to get logs of pod kube-scheduler-capz-conf-4dba30-control-plane-79kmh, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-4dba30-control-plane-79kmh)
Jan 20 21:03:40.380: INFO: Logs of kube-system/kube-scheduler-capz-conf-4dba30-control-plane-79kmh:kube-scheduler on node capz-conf-4dba30-control-plane-79kmh
Jan 20 21:03:40.380: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-4dba30-control-plane-79kmh:kube-scheduler
[FAILED] Error waiting for all pods to be running and ready: 3 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD NODE PHASE GRACE CONDITIONS
kube-apiserver-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
kube-controller-manager-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Pending []
kube-scheduler-capz-conf-4dba30-control-plane-79kmh capz-conf-4dba30-control-plane-79kmh Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-scheduler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-scheduler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-20 20:50:12 +0000 UTC Reason: Message:}]
In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/20/23 21:03:40.38
< Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/20/23 21:03:40.38 (10m35.915s)
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.467from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.467
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.461from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.461
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.466from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.466
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.461from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.461
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.451
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.46from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.46
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.454from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.454
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.465from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.465
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.467from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.467
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\]$'
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.452from junit.kubetest.01.xml
[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m The first SynchronizedBeforeSuite function running on Ginkgo parallel process #1 failed. This suite will now abort. In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:77 @ 01/20/23 21:03:40.452
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
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