PR #110981 pull-kubernetes-e2e-capz-conformance #1611295111432376320
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | claudiubelu: DO NOT MERGE: Windows unit tests |
| Result | SUCCESS |
| Tests | 25 failed / 27 succeeded |
| Started | |
| Elapsed | 57m19s |
| Revision | a5812297aa4eb2ce1adaecd9ceab632756bdb601 |
| Refs |
110981 |
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
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/06/23 10:27:43.126from 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/06/23 10:27:43.126
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/06/23 10:27:43.126from 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/06/23 10:27:43.126
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
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/06/23 10:27:43.123from 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/06/23 10:27:43.123
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
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/06/23 10:27:43.121from 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/06/23 10:27:43.121
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/06/23 10:27:43.121from 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/06/23 10:27:43.121
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/06/23 10:27:43.127from 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/06/23 10:27:43.127
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/06/23 10:27:43.126from 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/06/23 10:27:43.126
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/06/23 10:27:43.121from 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/06/23 10:27:43.121
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/06/23 10:27:43.124from 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/06/23 10:27:43.124
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/06/23 10:27:43.124from 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/06/23 10:27:43.124
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/06/23 10:27:43.121from 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/06/23 10:27:43.121
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
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/06/23 10:27:43.124from 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/06/23 10:27:43.124
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/06/23 10:27:43.128from 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/06/23 10:27:43.128
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-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-controller-manager]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-controller-manager]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason: Message:}]
kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +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-06 10:14:35 +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-06 10:14:35 +0000 UTC Reason: Message:}]
In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/06/23 10:27:43.069
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/06/23 10:17:36.48
Jan 6 10:17:36.480: INFO: >>> kubeConfig: /tmp/kubeconfig
Jan 6 10:17:36.483: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Jan 6 10:17:36.967: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Jan 6 10:17:37.522: INFO: The status of Pod calico-node-89tz8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:37.522: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:37.522: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:37.522: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:37.522: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Jan 6 10:17:37.522: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:37.522: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:37.522: INFO: calico-node-89tz8 capz-conf-n0e3dg-md-0-ztsnc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:33 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:06 +0000 UTC }]
Jan 6 10:17:37.522: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:37.522: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:37.522: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:37.522: INFO:
Jan 6 10:17:39.917: INFO: The status of Pod calico-node-89tz8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:39.917: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:39.917: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:39.917: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:39.917: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Jan 6 10:17:39.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:39.917: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:39.917: INFO: calico-node-89tz8 capz-conf-n0e3dg-md-0-ztsnc Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:33 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:06 +0000 UTC }]
Jan 6 10:17:39.917: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:39.917: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:39.917: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:39.917: INFO:
Jan 6 10:17:41.909: INFO: The status of Pod calico-node-89tz8 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:41.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:41.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:41.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:41.909: INFO: 10 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Jan 6 10:17:41.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:41.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:41.909: INFO: calico-node-89tz8 capz-conf-n0e3dg-md-0-ztsnc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:33 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC ContainersNotReady containers with unready status: [calico-node]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:06 +0000 UTC }]
Jan 6 10:17:41.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:41.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:41.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:41.909: INFO:
Jan 6 10:17:43.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:43.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:43.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:43.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Jan 6 10:17:43.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:43.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:43.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:43.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:43.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:43.901: INFO:
Jan 6 10:17:45.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:45.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:45.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:45.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Jan 6 10:17:45.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:45.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:45.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:45.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:45.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:45.901: INFO:
Jan 6 10:17:47.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:47.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:47.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:47.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Jan 6 10:17:47.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:47.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:47.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:47.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:47.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:47.901: INFO:
Jan 6 10:17:49.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:49.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:49.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:49.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Jan 6 10:17:49.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:49.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:49.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:49.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:49.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:49.899: INFO:
Jan 6 10:17:51.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:51.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:51.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:51.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Jan 6 10:17:51.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:51.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:51.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:51.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:51.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:51.907: INFO:
Jan 6 10:17:53.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:53.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:53.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:53.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Jan 6 10:17:53.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:53.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:53.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:53.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:53.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:53.900: INFO:
Jan 6 10:17:55.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:55.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:55.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:55.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Jan 6 10:17:55.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:55.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:55.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:55.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:55.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:55.898: INFO:
Jan 6 10:17:57.911: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:57.911: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:57.911: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:57.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Jan 6 10:17:57.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:57.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:57.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:57.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:57.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:57.911: INFO:
Jan 6 10:17:59.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:59.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:59.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:17:59.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Jan 6 10:17:59.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:17:59.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:17:59.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:17:59.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:59.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:17:59.898: INFO:
Jan 6 10:18:01.929: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:01.929: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:01.929: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:01.929: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Jan 6 10:18:01.929: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:01.929: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:01.929: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:01.929: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:01.929: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:01.929: INFO:
Jan 6 10:18:03.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:03.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:03.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:03.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Jan 6 10:18:03.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:03.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:03.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:03.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:03.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:03.898: INFO:
Jan 6 10:18:05.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:05.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:05.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:05.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Jan 6 10:18:05.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:05.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:05.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:05.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:05.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:05.901: INFO:
Jan 6 10:18:07.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:07.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:07.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:07.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Jan 6 10:18:07.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:07.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:07.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:07.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:07.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:07.897: INFO:
Jan 6 10:18:09.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:09.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:09.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:09.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Jan 6 10:18:09.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:09.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:09.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:09.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:09.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:09.898: INFO:
Jan 6 10:18:11.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:11.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:11.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:11.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Jan 6 10:18:11.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:11.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:11.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:11.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:11.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:11.904: INFO:
Jan 6 10:18:13.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:13.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:13.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:13.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Jan 6 10:18:13.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:13.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:13.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:13.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:13.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:13.897: INFO:
Jan 6 10:18:15.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:15.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:15.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:15.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Jan 6 10:18:15.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:15.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:15.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:15.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:15.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:15.901: INFO:
Jan 6 10:18:17.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:17.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:17.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:17.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Jan 6 10:18:17.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:17.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:17.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:17.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:17.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:17.897: INFO:
Jan 6 10:18:19.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:19.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:19.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:19.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Jan 6 10:18:19.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:19.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:19.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:19.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:19.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:19.895: INFO:
Jan 6 10:18:21.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:21.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:21.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:21.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Jan 6 10:18:21.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:21.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:21.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:21.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:21.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:21.900: INFO:
Jan 6 10:18:23.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:23.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:23.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:23.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Jan 6 10:18:23.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:23.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:23.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:23.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:23.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:23.901: INFO:
Jan 6 10:18:25.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:25.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:25.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:25.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Jan 6 10:18:25.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:25.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:25.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:25.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:25.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:25.899: INFO:
Jan 6 10:18:28.100: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:28.100: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:28.100: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:28.100: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (51 seconds elapsed)
Jan 6 10:18:28.100: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:28.100: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:28.100: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:28.100: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:28.100: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:28.100: INFO:
Jan 6 10:18:29.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:29.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:29.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:29.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Jan 6 10:18:29.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:29.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:29.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:29.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:29.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:29.906: INFO:
Jan 6 10:18:31.915: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:31.915: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:31.915: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:31.915: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Jan 6 10:18:31.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:31.915: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:31.915: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:31.915: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:31.915: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:31.915: INFO:
Jan 6 10:18:33.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:33.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:33.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:33.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Jan 6 10:18:33.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:33.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:33.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:33.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:33.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:33.898: INFO:
Jan 6 10:18:35.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:35.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:35.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:35.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Jan 6 10:18:35.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:35.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:35.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:35.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:35.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:35.899: INFO:
Jan 6 10:18:37.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:37.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:37.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:37.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Jan 6 10:18:37.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:37.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:37.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:37.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:37.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:37.899: INFO:
Jan 6 10:18:39.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:39.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:39.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:39.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Jan 6 10:18:39.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:39.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:39.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:39.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:39.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:39.899: INFO:
Jan 6 10:18:41.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:41.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:41.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:41.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Jan 6 10:18:41.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:41.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:41.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:41.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:41.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:41.904: INFO:
Jan 6 10:18:43.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:43.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:43.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:43.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Jan 6 10:18:43.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:43.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:43.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:43.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:43.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:43.897: INFO:
Jan 6 10:18:45.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:45.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:45.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:45.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Jan 6 10:18:45.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:45.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:45.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:45.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:45.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:45.900: INFO:
Jan 6 10:18:47.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:47.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:47.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:47.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Jan 6 10:18:47.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:47.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:47.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:47.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:47.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:47.898: INFO:
Jan 6 10:18:49.912: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:49.912: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:49.912: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Jan 6 10:18:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:49.912: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:49.912: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:49.912: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:49.912: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:49.912: INFO:
Jan 6 10:18:51.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:51.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:51.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:51.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Jan 6 10:18:51.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:51.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:51.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:51.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:51.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:51.899: INFO:
Jan 6 10:18:53.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:53.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:53.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:53.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Jan 6 10:18:53.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:53.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:53.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:53.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:53.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:53.903: INFO:
Jan 6 10:18:55.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:55.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:55.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:55.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Jan 6 10:18:55.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:55.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:55.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:55.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:55.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:55.906: INFO:
Jan 6 10:18:57.913: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:57.913: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:57.913: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:57.913: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Jan 6 10:18:57.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:57.913: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:57.913: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:57.913: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:57.913: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:57.913: INFO:
Jan 6 10:18:59.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:59.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:59.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:18:59.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Jan 6 10:18:59.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:18:59.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:18:59.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:18:59.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:59.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:18:59.900: INFO:
Jan 6 10:19:01.917: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:01.918: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:01.918: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:01.918: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Jan 6 10:19:01.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:01.918: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:01.918: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:01.918: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:01.918: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:01.918: INFO:
Jan 6 10:19:03.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:03.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:03.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:03.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Jan 6 10:19:03.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:03.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:03.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:03.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:03.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:03.905: INFO:
Jan 6 10:19:05.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:05.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:05.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:05.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Jan 6 10:19:05.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:05.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:05.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:05.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:05.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:05.904: INFO:
Jan 6 10:19:07.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:07.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:07.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:07.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Jan 6 10:19:07.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:07.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:07.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:07.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:07.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:07.903: INFO:
Jan 6 10:19:09.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:09.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:09.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:09.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Jan 6 10:19:09.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:09.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:09.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:09.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:09.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:09.897: INFO:
Jan 6 10:19:11.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:11.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:11.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:11.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Jan 6 10:19:11.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:11.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:11.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:11.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:11.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:11.910: INFO:
Jan 6 10:19:13.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:13.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:13.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:13.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Jan 6 10:19:13.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:13.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:13.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:13.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:13.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:13.905: INFO:
Jan 6 10:19:15.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:15.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:15.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:15.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Jan 6 10:19:15.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:15.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:15.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:15.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:15.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:15.907: INFO:
Jan 6 10:19:17.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:17.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:17.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:17.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Jan 6 10:19:17.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:17.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:17.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:17.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:17.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:17.907: INFO:
Jan 6 10:19:19.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:19.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:19.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:19.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Jan 6 10:19:19.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:19.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:19.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:19.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:19.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:19.904: INFO:
Jan 6 10:19:21.911: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:21.911: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:21.911: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:21.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Jan 6 10:19:21.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:21.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:21.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:21.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:21.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:21.911: INFO:
Jan 6 10:19:23.915: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:23.915: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:23.915: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:23.915: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Jan 6 10:19:23.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:23.915: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:23.915: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:23.915: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:23.915: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:23.916: INFO:
Jan 6 10:19:25.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:25.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:25.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:25.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Jan 6 10:19:25.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:25.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:25.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:25.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:25.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:25.907: INFO:
Jan 6 10:19:27.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:27.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:27.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:27.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Jan 6 10:19:27.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:27.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:27.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:27.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:27.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:27.905: INFO:
Jan 6 10:19:29.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:29.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:29.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:29.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Jan 6 10:19:29.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:29.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:29.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:29.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:29.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:29.909: INFO:
Jan 6 10:19:31.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:31.910: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:31.910: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:31.910: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Jan 6 10:19:31.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:31.910: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:31.910: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:31.910: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:31.910: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:31.910: INFO:
Jan 6 10:19:33.914: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:33.914: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:33.914: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:33.914: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Jan 6 10:19:33.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:33.914: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:33.914: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:33.914: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:33.914: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:33.914: INFO:
Jan 6 10:19:35.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:35.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:35.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:35.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Jan 6 10:19:35.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:35.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:35.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:35.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:35.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:35.902: INFO:
Jan 6 10:19:37.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:37.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:37.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:37.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Jan 6 10:19:37.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:37.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:37.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:37.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:37.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:37.901: INFO:
Jan 6 10:19:39.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:39.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:39.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:39.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Jan 6 10:19:39.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:39.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:39.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:39.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:39.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:39.900: INFO:
Jan 6 10:19:41.912: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:41.912: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:41.912: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:41.912: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Jan 6 10:19:41.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:41.912: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:41.912: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:41.912: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:41.912: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:41.912: INFO:
Jan 6 10:19:43.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:43.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:43.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:43.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Jan 6 10:19:43.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:43.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:43.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:43.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:43.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:43.897: INFO:
Jan 6 10:19:45.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:45.910: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:45.910: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:45.910: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Jan 6 10:19:45.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:45.910: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:45.910: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:45.910: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:45.910: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:45.910: INFO:
Jan 6 10:19:47.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:47.910: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:47.910: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:47.910: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Jan 6 10:19:47.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:47.910: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:47.910: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:47.910: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:47.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:47.911: INFO:
Jan 6 10:19:49.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:49.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:49.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:49.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Jan 6 10:19:49.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:49.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:49.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:49.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:49.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:49.903: INFO:
Jan 6 10:19:51.918: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:51.918: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:51.918: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:51.918: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Jan 6 10:19:51.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:51.918: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:51.918: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:51.918: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:51.919: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:51.919: INFO:
Jan 6 10:19:53.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:53.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:53.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:53.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Jan 6 10:19:53.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:53.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:53.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:53.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:53.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:53.907: INFO:
Jan 6 10:19:55.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:55.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:55.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:55.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Jan 6 10:19:55.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:55.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:55.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:55.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:55.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:55.907: INFO:
Jan 6 10:19:57.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:57.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:57.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:57.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Jan 6 10:19:57.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:57.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:57.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:57.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:57.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:57.905: INFO:
Jan 6 10:19:59.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:59.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:59.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:19:59.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Jan 6 10:19:59.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:19:59.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:19:59.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:19:59.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:59.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:19:59.904: INFO:
Jan 6 10:20:02.118: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:02.118: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:02.119: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:02.119: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (145 seconds elapsed)
Jan 6 10:20:02.119: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:02.119: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:02.119: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:02.119: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:02.119: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:02.119: INFO:
Jan 6 10:20:03.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:03.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:03.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:03.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Jan 6 10:20:03.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:03.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:03.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:03.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:03.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:03.907: INFO:
Jan 6 10:20:05.916: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:05.916: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:05.916: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:05.916: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Jan 6 10:20:05.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:05.916: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:05.916: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:05.916: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:05.916: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:05.916: INFO:
Jan 6 10:20:07.915: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:07.915: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:07.915: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:07.915: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Jan 6 10:20:07.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:07.915: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:07.915: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:07.915: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:07.915: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:07.915: INFO:
Jan 6 10:20:09.918: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:09.918: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:09.919: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:09.919: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Jan 6 10:20:09.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:09.919: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:09.919: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:09.919: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:09.919: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:09.919: INFO:
Jan 6 10:20:11.925: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:11.925: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:11.925: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:11.925: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Jan 6 10:20:11.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:11.925: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:11.925: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:11.925: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:11.925: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:11.925: INFO:
Jan 6 10:20:14.104: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:14.104: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:14.104: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:14.104: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (157 seconds elapsed)
Jan 6 10:20:14.104: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:14.104: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:14.104: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:14.104: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:14.104: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:14.104: INFO:
Jan 6 10:20:15.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:15.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:15.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:15.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Jan 6 10:20:15.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:15.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:15.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:15.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:15.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:15.904: INFO:
Jan 6 10:20:17.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:17.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:17.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:17.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Jan 6 10:20:17.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:17.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:17.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:17.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:17.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:17.903: INFO:
Jan 6 10:20:19.915: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:19.915: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:19.915: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:19.915: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Jan 6 10:20:19.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:19.915: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:19.915: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:19.915: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:19.915: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:19.915: INFO:
Jan 6 10:20:21.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:21.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:21.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:21.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Jan 6 10:20:21.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:21.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:21.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:21.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:21.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:21.907: INFO:
Jan 6 10:20:23.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:23.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:23.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:23.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Jan 6 10:20:23.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:23.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:23.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:23.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:23.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:23.902: INFO:
Jan 6 10:20:26.101: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:26.101: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:26.101: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:26.101: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (169 seconds elapsed)
Jan 6 10:20:26.101: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:26.101: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:26.101: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:26.101: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:26.101: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:26.101: INFO:
Jan 6 10:20:27.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:27.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:27.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:27.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Jan 6 10:20:27.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:27.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:27.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:27.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:27.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:27.903: INFO:
Jan 6 10:20:29.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:29.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:29.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:29.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Jan 6 10:20:29.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:29.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:29.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:29.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:29.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:29.909: INFO:
Jan 6 10:20:31.926: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:31.926: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:31.926: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:31.926: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Jan 6 10:20:31.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:31.926: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:31.926: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:31.926: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:31.926: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:31.926: INFO:
Jan 6 10:20:33.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:33.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:33.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:33.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Jan 6 10:20:33.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:33.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:33.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:33.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:33.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:33.902: INFO:
Jan 6 10:20:35.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:35.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:35.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:35.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Jan 6 10:20:35.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:35.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:35.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:35.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:35.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:35.902: INFO:
Jan 6 10:20:37.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:37.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:37.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:37.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Jan 6 10:20:37.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:37.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:37.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:37.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:37.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:37.901: INFO:
Jan 6 10:20:39.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:39.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:39.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:39.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Jan 6 10:20:39.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:39.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:39.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:39.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:39.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:39.903: INFO:
Jan 6 10:20:41.916: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:41.916: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:41.916: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:41.916: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Jan 6 10:20:41.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:41.916: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:41.916: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:41.917: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:41.917: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:41.917: INFO:
Jan 6 10:20:43.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:43.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:43.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:43.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Jan 6 10:20:43.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:43.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:43.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:43.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:43.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:43.905: INFO:
Jan 6 10:20:45.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:45.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:45.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:45.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Jan 6 10:20:45.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:45.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:45.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:45.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:45.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:45.899: INFO:
Jan 6 10:20:47.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:47.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:47.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:47.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Jan 6 10:20:47.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:47.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:47.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:47.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:47.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:47.906: INFO:
Jan 6 10:20:49.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:49.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:49.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:49.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Jan 6 10:20:49.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:49.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:49.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:49.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:49.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:49.899: INFO:
Jan 6 10:20:52.111: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:52.111: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:52.111: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:52.111: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (195 seconds elapsed)
Jan 6 10:20:52.111: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:52.111: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:52.111: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:52.111: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:52.111: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:52.111: INFO:
Jan 6 10:20:53.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:53.908: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:53.908: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:53.908: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Jan 6 10:20:53.908: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:53.908: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:53.908: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:53.908: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:53.908: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:53.908: INFO:
Jan 6 10:20:55.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:55.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:55.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:55.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Jan 6 10:20:55.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:55.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:55.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:55.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:55.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:55.909: INFO:
Jan 6 10:20:57.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:57.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:57.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:57.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Jan 6 10:20:57.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:57.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:57.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:57.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:57.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:57.905: INFO:
Jan 6 10:20:59.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:59.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:59.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:20:59.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Jan 6 10:20:59.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:20:59.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:20:59.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:20:59.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:59.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:20:59.909: INFO:
Jan 6 10:21:01.927: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:01.927: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:01.927: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:01.927: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Jan 6 10:21:01.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:01.927: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:01.927: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:01.927: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:01.927: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:01.927: INFO:
Jan 6 10:21:03.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:03.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:03.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:03.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Jan 6 10:21:03.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:03.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:03.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:03.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:03.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:03.903: INFO:
Jan 6 10:21:05.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:05.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:05.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:05.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Jan 6 10:21:05.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:05.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:05.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:05.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:05.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:05.902: INFO:
Jan 6 10:21:07.911: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:07.911: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:07.911: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:07.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Jan 6 10:21:07.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:07.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:07.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:07.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:07.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:07.911: INFO:
Jan 6 10:21:09.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:09.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:09.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:09.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Jan 6 10:21:09.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:09.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:09.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:09.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:09.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:09.904: INFO:
Jan 6 10:21:11.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:11.910: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:11.910: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:11.910: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Jan 6 10:21:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:11.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:11.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:11.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:11.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:11.911: INFO:
Jan 6 10:21:13.911: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:13.911: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:13.911: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:13.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Jan 6 10:21:13.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:13.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:13.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:13.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:13.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:13.911: INFO:
Jan 6 10:21:15.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:15.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:15.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:15.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Jan 6 10:21:15.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:15.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:15.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:15.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:15.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:15.901: INFO:
Jan 6 10:21:17.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:17.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:17.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:17.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Jan 6 10:21:17.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:17.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:17.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:17.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:17.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:17.903: INFO:
Jan 6 10:21:19.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:19.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:19.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:19.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Jan 6 10:21:19.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:19.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:19.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:19.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:19.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:19.900: INFO:
Jan 6 10:21:21.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:21.908: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:21.908: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:21.908: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Jan 6 10:21:21.908: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:21.908: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:21.908: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:21.908: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:21.908: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:21.908: INFO:
Jan 6 10:21:23.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:23.910: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:23.910: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:23.910: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Jan 6 10:21:23.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:23.910: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:23.910: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:23.910: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:23.910: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:23.910: INFO:
Jan 6 10:21:25.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:25.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:25.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:25.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Jan 6 10:21:25.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:25.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:25.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:25.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:25.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:25.901: INFO:
Jan 6 10:21:28.103: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:28.103: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:28.103: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:28.103: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (231 seconds elapsed)
Jan 6 10:21:28.103: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:28.103: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:28.103: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:28.103: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:28.103: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:28.103: INFO:
Jan 6 10:21:29.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:29.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:29.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:29.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Jan 6 10:21:29.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:29.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:29.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:29.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:29.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:29.899: INFO:
Jan 6 10:21:31.912: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:31.912: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:31.912: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:31.912: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Jan 6 10:21:31.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:31.912: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:31.912: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:31.912: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:31.912: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:31.912: INFO:
Jan 6 10:21:33.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:33.908: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:33.908: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:33.908: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Jan 6 10:21:33.908: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:33.908: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:33.908: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:33.908: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:33.908: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:33.908: INFO:
Jan 6 10:21:35.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:35.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:35.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:35.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Jan 6 10:21:35.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:35.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:35.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:35.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:35.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:35.909: INFO:
Jan 6 10:21:37.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:37.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:37.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:37.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Jan 6 10:21:37.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:37.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:37.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:37.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:37.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:37.905: INFO:
Jan 6 10:21:39.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:39.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:39.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:39.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Jan 6 10:21:39.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:39.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:39.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:39.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:39.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:39.907: INFO:
Jan 6 10:21:41.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:41.911: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:41.911: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:41.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Jan 6 10:21:41.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:41.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:41.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:41.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:41.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:41.911: INFO:
Jan 6 10:21:43.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:43.908: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:43.908: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:43.908: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Jan 6 10:21:43.908: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:43.908: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:43.908: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:43.908: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:43.908: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:43.908: INFO:
Jan 6 10:21:45.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:45.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:45.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:45.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Jan 6 10:21:45.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:45.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:45.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:45.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:45.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:45.905: INFO:
Jan 6 10:21:47.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:47.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:47.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:47.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Jan 6 10:21:47.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:47.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:47.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:47.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:47.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:47.900: INFO:
Jan 6 10:21:49.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:49.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:49.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:49.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Jan 6 10:21:49.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:49.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:49.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:49.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:49.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:49.905: INFO:
Jan 6 10:21:51.917: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:51.917: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:51.917: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:51.917: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Jan 6 10:21:51.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:51.917: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:51.917: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:51.917: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:51.917: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:51.917: INFO:
Jan 6 10:21:53.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:53.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:53.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:53.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Jan 6 10:21:53.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:53.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:53.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:53.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:53.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:53.906: INFO:
Jan 6 10:21:55.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:55.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:55.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:55.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Jan 6 10:21:55.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:55.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:55.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:55.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:55.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:55.902: INFO:
Jan 6 10:21:57.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:57.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:57.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:57.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Jan 6 10:21:57.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:57.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:57.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:57.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:57.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:57.904: INFO:
Jan 6 10:21:59.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:59.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:59.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:21:59.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Jan 6 10:21:59.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:21:59.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:21:59.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:21:59.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:59.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:21:59.906: INFO:
Jan 6 10:22:01.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:01.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:01.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:01.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Jan 6 10:22:01.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:01.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:01.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:01.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:01.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:01.903: INFO:
Jan 6 10:22:03.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:03.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:03.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:03.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Jan 6 10:22:03.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:03.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:03.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:03.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:03.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:03.900: INFO:
Jan 6 10:22:05.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:05.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:05.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:05.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Jan 6 10:22:05.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:05.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:05.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:05.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:05.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:05.907: INFO:
Jan 6 10:22:07.912: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:07.912: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:07.912: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:07.912: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Jan 6 10:22:07.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:07.912: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:07.912: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:07.912: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:07.912: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:07.912: INFO:
Jan 6 10:22:10.099: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:10.099: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:10.099: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:10.099: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (273 seconds elapsed)
Jan 6 10:22:10.099: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:10.099: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:10.099: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:10.099: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:10.099: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:10.099: INFO:
Jan 6 10:22:11.927: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:11.927: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:11.927: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:11.927: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Jan 6 10:22:11.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:11.927: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:11.927: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:11.927: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:11.927: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:11.927: INFO:
Jan 6 10:22:13.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:13.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:13.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:13.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Jan 6 10:22:13.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:13.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:13.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:13.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:13.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:13.905: INFO:
Jan 6 10:22:15.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:15.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:15.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:15.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Jan 6 10:22:15.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:15.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:15.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:15.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:15.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:15.899: INFO:
Jan 6 10:22:17.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:17.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:17.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:17.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Jan 6 10:22:17.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:17.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:17.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:17.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:17.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:17.902: INFO:
Jan 6 10:22:19.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:19.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:19.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:19.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Jan 6 10:22:19.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:19.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:19.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:19.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:19.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:19.905: INFO:
Jan 6 10:22:21.945: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:21.945: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:21.945: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:21.945: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Jan 6 10:22:21.945: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:21.945: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:21.945: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:21.945: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:21.945: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:21.945: INFO:
Jan 6 10:22:23.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:23.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:23.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:23.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Jan 6 10:22:23.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:23.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:23.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:23.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:23.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:23.902: INFO:
Jan 6 10:22:25.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:25.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:25.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:25.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Jan 6 10:22:25.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:25.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:25.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:25.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:25.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:25.905: INFO:
Jan 6 10:22:27.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:27.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:27.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:27.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Jan 6 10:22:27.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:27.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:27.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:27.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:27.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:27.903: INFO:
Jan 6 10:22:29.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:29.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:29.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:29.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Jan 6 10:22:29.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:29.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:29.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:29.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:29.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:29.899: INFO:
Jan 6 10:22:31.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:31.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:31.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:31.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Jan 6 10:22:31.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:31.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:31.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:31.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:31.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:31.907: INFO:
Jan 6 10:22:34.098: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:34.098: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:34.098: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:34.098: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (297 seconds elapsed)
Jan 6 10:22:34.098: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:34.098: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:34.098: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:34.098: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:34.098: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:34.098: INFO:
Jan 6 10:22:35.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:35.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:35.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:35.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Jan 6 10:22:35.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:35.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:35.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:35.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:35.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:35.900: INFO:
Jan 6 10:22:37.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:37.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:37.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:37.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Jan 6 10:22:37.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:37.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:37.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:37.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:37.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:37.905: INFO:
Jan 6 10:22:39.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:39.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:39.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:39.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Jan 6 10:22:39.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:39.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:39.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:39.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:39.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:39.900: INFO:
Jan 6 10:22:41.910: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:41.910: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:41.910: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:41.910: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Jan 6 10:22:41.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:41.910: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:41.910: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:41.910: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:41.910: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:41.910: INFO:
Jan 6 10:22:43.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:43.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:43.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:43.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Jan 6 10:22:43.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:43.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:43.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:43.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:43.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:43.906: INFO:
Jan 6 10:22:45.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:45.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:45.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:45.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Jan 6 10:22:45.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:45.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:45.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:45.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:45.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:45.905: INFO:
Jan 6 10:22:47.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:47.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:47.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:47.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Jan 6 10:22:47.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:47.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:47.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:47.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:47.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:47.905: INFO:
Jan 6 10:22:49.913: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:49.913: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:49.914: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:49.914: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Jan 6 10:22:49.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:49.914: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:49.914: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:49.914: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:49.914: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:49.914: INFO:
Jan 6 10:22:51.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:51.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:51.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:51.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Jan 6 10:22:51.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:51.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:51.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:51.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:51.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:51.904: INFO:
Jan 6 10:22:53.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:53.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:53.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:53.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Jan 6 10:22:53.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:53.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:53.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:53.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:53.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:53.906: INFO:
Jan 6 10:22:55.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:55.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:55.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:55.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Jan 6 10:22:55.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:55.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:55.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:55.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:55.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:55.901: INFO:
Jan 6 10:22:57.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:57.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:57.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:57.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Jan 6 10:22:57.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:57.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:57.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:57.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:57.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:57.896: INFO:
Jan 6 10:22:59.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:59.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:59.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:22:59.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Jan 6 10:22:59.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:22:59.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:22:59.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:22:59.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:59.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:22:59.899: INFO:
Jan 6 10:23:01.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:01.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:01.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:01.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Jan 6 10:23:01.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:01.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:01.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:01.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:01.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:01.905: INFO:
Jan 6 10:23:03.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:03.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:03.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:03.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Jan 6 10:23:03.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:03.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:03.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:03.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:03.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:03.909: INFO:
Jan 6 10:23:05.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:05.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:05.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:05.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Jan 6 10:23:05.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:05.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:05.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:05.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:05.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:05.903: INFO:
Jan 6 10:23:07.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:07.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:07.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:07.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Jan 6 10:23:07.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:07.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:07.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:07.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:07.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:07.901: INFO:
Jan 6 10:23:09.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:09.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:09.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:09.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Jan 6 10:23:09.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:09.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:09.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:09.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:09.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:09.897: INFO:
Jan 6 10:23:11.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:11.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:11.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:11.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Jan 6 10:23:11.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:11.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:11.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:11.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:11.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:11.902: INFO:
Jan 6 10:23:13.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:13.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:13.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:13.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Jan 6 10:23:13.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:13.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:13.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:13.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:13.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:13.899: INFO:
Jan 6 10:23:15.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:15.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:15.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:15.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Jan 6 10:23:15.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:15.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:15.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:15.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:15.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:15.909: INFO:
Jan 6 10:23:17.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:17.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:17.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:17.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Jan 6 10:23:17.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:17.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:17.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:17.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:17.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:17.899: INFO:
Jan 6 10:23:19.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:19.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:19.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:19.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Jan 6 10:23:19.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:19.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:19.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:19.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:19.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:19.905: INFO:
Jan 6 10:23:21.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:21.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:21.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:21.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Jan 6 10:23:21.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:21.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:21.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:21.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:21.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:21.904: INFO:
Jan 6 10:23:23.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:23.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:23.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:23.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Jan 6 10:23:23.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:23.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:23.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:23.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:23.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:23.904: INFO:
Jan 6 10:23:25.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:25.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:25.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:25.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Jan 6 10:23:25.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:25.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:25.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:25.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:25.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:25.900: INFO:
Jan 6 10:23:27.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:27.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:27.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:27.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Jan 6 10:23:27.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:27.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:27.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:27.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:27.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:27.900: INFO:
Jan 6 10:23:29.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:29.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:29.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:29.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Jan 6 10:23:29.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:29.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:29.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:29.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:29.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:29.898: INFO:
Jan 6 10:23:31.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:31.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:31.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:31.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Jan 6 10:23:31.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:31.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:31.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:31.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:31.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:31.904: INFO:
Jan 6 10:23:33.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:33.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:33.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:33.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Jan 6 10:23:33.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:33.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:33.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:33.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:33.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:33.902: INFO:
Jan 6 10:23:35.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:35.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:35.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:35.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Jan 6 10:23:35.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:35.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:35.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:35.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:35.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:35.899: INFO:
Jan 6 10:23:37.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:37.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:37.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:37.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Jan 6 10:23:37.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:37.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:37.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:37.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:37.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:37.899: INFO:
Jan 6 10:23:39.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:39.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:39.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:39.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Jan 6 10:23:39.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:39.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:39.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:39.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:39.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:39.898: INFO:
Jan 6 10:23:41.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:41.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:41.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:41.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Jan 6 10:23:41.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:41.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:41.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:41.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:41.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:41.900: INFO:
Jan 6 10:23:43.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:43.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:43.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:43.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Jan 6 10:23:43.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:43.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:43.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:43.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:43.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:43.895: INFO:
Jan 6 10:23:45.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:45.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:45.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:45.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Jan 6 10:23:45.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:45.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:45.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:45.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:45.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:45.897: INFO:
Jan 6 10:23:47.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:47.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:47.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:47.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Jan 6 10:23:47.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:47.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:47.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:47.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:47.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:47.896: INFO:
Jan 6 10:23:49.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:49.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:49.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:49.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Jan 6 10:23:49.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:49.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:49.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:49.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:49.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:49.900: INFO:
Jan 6 10:23:51.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:51.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:51.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:51.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Jan 6 10:23:51.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:51.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:51.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:51.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:51.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:51.900: INFO:
Jan 6 10:23:53.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:53.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:53.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:53.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Jan 6 10:23:53.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:53.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:53.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:53.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:53.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:53.898: INFO:
Jan 6 10:23:55.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:55.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:55.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:55.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Jan 6 10:23:55.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:55.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:55.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:55.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:55.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:55.897: INFO:
Jan 6 10:23:57.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:57.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:57.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:57.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Jan 6 10:23:57.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:57.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:57.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:57.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:57.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:57.896: INFO:
Jan 6 10:23:59.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:59.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:59.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:23:59.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Jan 6 10:23:59.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:23:59.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:23:59.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:23:59.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:59.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:23:59.900: INFO:
Jan 6 10:24:01.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:01.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:01.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:01.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Jan 6 10:24:01.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:01.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:01.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:01.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:01.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:01.898: INFO:
Jan 6 10:24:03.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:03.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:03.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:03.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Jan 6 10:24:03.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:03.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:03.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:03.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:03.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:03.896: INFO:
Jan 6 10:24:05.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:05.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:05.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:05.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Jan 6 10:24:05.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:05.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:05.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:05.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:05.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:05.898: INFO:
Jan 6 10:24:07.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:07.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:07.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:07.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Jan 6 10:24:07.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:07.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:07.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:07.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:07.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:07.897: INFO:
Jan 6 10:24:09.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:09.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:09.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:09.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Jan 6 10:24:09.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:09.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:09.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:09.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:09.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:09.896: INFO:
Jan 6 10:24:11.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:11.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:11.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:11.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Jan 6 10:24:11.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:11.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:11.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:11.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:11.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:11.898: INFO:
Jan 6 10:24:13.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:13.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:13.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:13.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Jan 6 10:24:13.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:13.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:13.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:13.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:13.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:13.901: INFO:
Jan 6 10:24:15.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:15.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:15.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:15.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Jan 6 10:24:15.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:15.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:15.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:15.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:15.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:15.902: INFO:
Jan 6 10:24:17.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:17.908: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:17.908: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:17.908: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Jan 6 10:24:17.908: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:17.908: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:17.908: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:17.908: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:17.908: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:17.908: INFO:
Jan 6 10:24:19.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:19.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:19.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:19.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Jan 6 10:24:19.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:19.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:19.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:19.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:19.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:19.897: INFO:
Jan 6 10:24:21.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:21.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:21.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:21.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Jan 6 10:24:21.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:21.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:21.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:21.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:21.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:21.900: INFO:
Jan 6 10:24:23.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:23.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:23.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:23.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Jan 6 10:24:23.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:23.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:23.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:23.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:23.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:23.898: INFO:
Jan 6 10:24:25.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:25.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:25.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:25.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Jan 6 10:24:25.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:25.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:25.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:25.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:25.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:25.904: INFO:
Jan 6 10:24:27.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:27.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:27.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:27.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Jan 6 10:24:27.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:27.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:27.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:27.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:27.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:27.897: INFO:
Jan 6 10:24:29.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:29.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:29.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:29.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Jan 6 10:24:29.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:29.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:29.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:29.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:29.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:29.906: INFO:
Jan 6 10:24:31.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:31.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:31.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:31.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Jan 6 10:24:31.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:31.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:31.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:31.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:31.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:31.907: INFO:
Jan 6 10:24:33.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:33.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:33.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:33.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Jan 6 10:24:33.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:33.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:33.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:33.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:33.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:33.897: INFO:
Jan 6 10:24:35.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:35.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:35.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:35.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Jan 6 10:24:35.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:35.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:35.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:35.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:35.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:35.899: INFO:
Jan 6 10:24:37.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:37.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:37.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:37.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Jan 6 10:24:37.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:37.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:37.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:37.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:37.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:37.898: INFO:
Jan 6 10:24:39.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:39.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:39.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:39.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Jan 6 10:24:39.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:39.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:39.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:39.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:39.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:39.896: INFO:
Jan 6 10:24:41.911: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:41.911: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:41.911: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:41.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Jan 6 10:24:41.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:41.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:41.911: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:41.911: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:41.911: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:41.911: INFO:
Jan 6 10:24:43.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:43.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:43.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:43.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Jan 6 10:24:43.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:43.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:43.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:43.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:43.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:43.900: INFO:
Jan 6 10:24:45.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:45.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:45.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:45.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Jan 6 10:24:45.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:45.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:45.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:45.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:45.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:45.897: INFO:
Jan 6 10:24:47.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:47.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:47.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:47.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Jan 6 10:24:47.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:47.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:47.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:47.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:47.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:47.896: INFO:
Jan 6 10:24:49.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:49.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:49.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:49.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Jan 6 10:24:49.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:49.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:49.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:49.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:49.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:49.898: INFO:
Jan 6 10:24:51.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:51.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:51.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:51.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Jan 6 10:24:51.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:51.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:51.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:51.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:51.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:51.902: INFO:
Jan 6 10:24:53.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:53.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:53.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:53.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Jan 6 10:24:53.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:53.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:53.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:53.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:53.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:53.902: INFO:
Jan 6 10:24:55.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:55.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:55.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:55.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Jan 6 10:24:55.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:55.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:55.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:55.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:55.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:55.895: INFO:
Jan 6 10:24:57.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:57.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:57.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:57.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Jan 6 10:24:57.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:57.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:57.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:57.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:57.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:57.898: INFO:
Jan 6 10:24:59.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:59.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:59.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:24:59.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Jan 6 10:24:59.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:24:59.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:24:59.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:24:59.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:59.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:24:59.903: INFO:
Jan 6 10:25:01.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:01.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:01.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:01.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Jan 6 10:25:01.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:01.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:01.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:01.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:01.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:01.903: INFO:
Jan 6 10:25:03.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:03.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:03.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:03.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Jan 6 10:25:03.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:03.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:03.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:03.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:03.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:03.896: INFO:
Jan 6 10:25:05.909: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:05.909: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:05.909: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:05.909: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Jan 6 10:25:05.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:05.909: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:05.909: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:05.909: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:05.909: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:05.909: INFO:
Jan 6 10:25:07.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:07.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:07.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:07.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Jan 6 10:25:07.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:07.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:07.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:07.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:07.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:07.898: INFO:
Jan 6 10:25:09.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:09.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:09.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:09.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Jan 6 10:25:09.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:09.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:09.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:09.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:09.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:09.898: INFO:
Jan 6 10:25:12.096: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:12.096: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:12.096: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:12.096: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (455 seconds elapsed)
Jan 6 10:25:12.096: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:12.096: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:12.096: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:12.096: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:12.096: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:12.096: INFO:
Jan 6 10:25:13.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:13.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:13.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:13.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Jan 6 10:25:13.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:13.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:13.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:13.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:13.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:13.897: INFO:
Jan 6 10:25:15.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:15.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:15.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:15.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Jan 6 10:25:15.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:15.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:15.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:15.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:15.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:15.897: INFO:
Jan 6 10:25:17.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:17.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:17.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:17.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Jan 6 10:25:17.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:17.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:17.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:17.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:17.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:17.898: INFO:
Jan 6 10:25:19.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:19.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:19.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:19.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Jan 6 10:25:19.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:19.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:19.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:19.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:19.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:19.897: INFO:
Jan 6 10:25:21.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:21.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:21.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:21.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Jan 6 10:25:21.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:21.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:21.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:21.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:21.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:21.902: INFO:
Jan 6 10:25:23.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:23.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:23.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:23.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Jan 6 10:25:23.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:23.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:23.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:23.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:23.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:23.902: INFO:
Jan 6 10:25:25.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:25.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:25.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:25.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Jan 6 10:25:25.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:25.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:25.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:25.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:25.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:25.896: INFO:
Jan 6 10:25:27.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:27.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:27.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:27.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Jan 6 10:25:27.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:27.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:27.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:27.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:27.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:27.897: INFO:
Jan 6 10:25:29.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:29.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:29.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:29.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Jan 6 10:25:29.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:29.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:29.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:29.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:29.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:29.901: INFO:
Jan 6 10:25:31.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:31.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:31.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:31.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Jan 6 10:25:31.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:31.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:31.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:31.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:31.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:31.901: INFO:
Jan 6 10:25:33.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:33.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:33.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:33.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Jan 6 10:25:33.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:33.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:33.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:33.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:33.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:33.896: INFO:
Jan 6 10:25:35.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:35.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:35.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:35.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Jan 6 10:25:35.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:35.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:35.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:35.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:35.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:35.898: INFO:
Jan 6 10:25:37.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:37.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:37.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:37.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Jan 6 10:25:37.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:37.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:37.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:37.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:37.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:37.901: INFO:
Jan 6 10:25:39.894: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:39.894: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:39.894: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:39.894: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Jan 6 10:25:39.894: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:39.894: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:39.894: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:39.894: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:39.894: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:39.894: INFO:
Jan 6 10:25:41.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:41.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:41.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:41.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Jan 6 10:25:41.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:41.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:41.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:41.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:41.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:41.901: INFO:
Jan 6 10:25:43.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:43.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:43.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:43.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Jan 6 10:25:43.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:43.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:43.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:43.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:43.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:43.900: INFO:
Jan 6 10:25:45.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:45.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:45.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:45.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Jan 6 10:25:45.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:45.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:45.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:45.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:45.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:45.899: INFO:
Jan 6 10:25:47.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:47.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:47.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:47.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Jan 6 10:25:47.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:47.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:47.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:47.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:47.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:47.901: INFO:
Jan 6 10:25:49.907: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:49.907: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:49.907: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:49.907: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Jan 6 10:25:49.907: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:49.907: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:49.907: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:49.907: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:49.907: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:49.907: INFO:
Jan 6 10:25:51.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:51.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:51.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:51.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Jan 6 10:25:51.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:51.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:51.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:51.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:51.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:51.898: INFO:
Jan 6 10:25:53.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:53.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:53.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:53.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Jan 6 10:25:53.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:53.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:53.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:53.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:53.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:53.901: INFO:
Jan 6 10:25:55.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:55.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:55.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:55.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Jan 6 10:25:55.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:55.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:55.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:55.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:55.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:55.897: INFO:
Jan 6 10:25:57.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:57.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:57.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:57.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Jan 6 10:25:57.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:57.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:57.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:57.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:57.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:57.897: INFO:
Jan 6 10:25:59.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:59.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:59.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:25:59.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Jan 6 10:25:59.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:25:59.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:25:59.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:25:59.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:59.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:25:59.897: INFO:
Jan 6 10:26:01.923: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:01.923: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:01.923: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:01.923: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Jan 6 10:26:01.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:01.923: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:01.923: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:01.923: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:01.923: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:01.923: INFO:
Jan 6 10:26:03.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:03.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:03.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:03.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Jan 6 10:26:03.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:03.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:03.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:03.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:03.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:03.897: INFO:
Jan 6 10:26:05.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:05.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:05.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:05.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Jan 6 10:26:05.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:05.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:05.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:05.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:05.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:05.902: INFO:
Jan 6 10:26:07.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:07.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:07.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:07.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Jan 6 10:26:07.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:07.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:07.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:07.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:07.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:07.900: INFO:
Jan 6 10:26:09.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:09.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:09.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:09.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Jan 6 10:26:09.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:09.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:09.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:09.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:09.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:09.899: INFO:
Jan 6 10:26:11.913: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:11.913: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:11.913: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:11.913: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Jan 6 10:26:11.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:11.913: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:11.913: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:11.913: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:11.913: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:11.913: INFO:
Jan 6 10:26:13.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:13.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:13.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:13.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Jan 6 10:26:13.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:13.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:13.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:13.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:13.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:13.895: INFO:
Jan 6 10:26:15.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:15.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:15.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:15.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Jan 6 10:26:15.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:15.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:15.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:15.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:15.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:15.900: INFO:
Jan 6 10:26:17.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:17.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:17.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:17.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Jan 6 10:26:17.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:17.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:17.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:17.903: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:17.903: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:17.903: INFO:
Jan 6 10:26:20.091: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:20.091: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:20.091: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:20.091: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (523 seconds elapsed)
Jan 6 10:26:20.091: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:20.091: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:20.091: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:20.091: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:20.091: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:20.091: INFO:
Jan 6 10:26:21.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:21.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:21.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:21.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Jan 6 10:26:21.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:21.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:21.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:21.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:21.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:21.901: INFO:
Jan 6 10:26:23.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:23.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:23.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:23.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Jan 6 10:26:23.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:23.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:23.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:23.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:23.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:23.898: INFO:
Jan 6 10:26:25.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:25.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:25.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:25.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Jan 6 10:26:25.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:25.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:25.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:25.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:25.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:25.896: INFO:
Jan 6 10:26:27.905: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:27.905: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:27.905: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:27.905: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Jan 6 10:26:27.905: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:27.905: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:27.905: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:27.905: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:27.905: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:27.905: INFO:
Jan 6 10:26:29.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:29.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:29.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:29.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Jan 6 10:26:29.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:29.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:29.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:29.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:29.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:29.900: INFO:
Jan 6 10:26:31.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:31.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:31.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:31.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Jan 6 10:26:31.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:31.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:31.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:31.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:31.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:31.904: INFO:
Jan 6 10:26:33.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:33.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:33.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:33.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Jan 6 10:26:33.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:33.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:33.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:33.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:33.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:33.896: INFO:
Jan 6 10:26:35.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:35.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:35.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:35.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Jan 6 10:26:35.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:35.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:35.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:35.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:35.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:35.900: INFO:
Jan 6 10:26:37.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:37.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:37.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:37.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Jan 6 10:26:37.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:37.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:37.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:37.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:37.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:37.896: INFO:
Jan 6 10:26:39.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:39.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:39.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:39.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Jan 6 10:26:39.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:39.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:39.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:39.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:39.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:39.901: INFO:
Jan 6 10:26:41.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:41.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:41.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:41.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Jan 6 10:26:41.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:41.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:41.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:41.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:41.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:41.901: INFO:
Jan 6 10:26:43.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:43.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:43.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:43.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Jan 6 10:26:43.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:43.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:43.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:43.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:43.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:43.897: INFO:
Jan 6 10:26:45.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:45.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:45.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:45.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Jan 6 10:26:45.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:45.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:45.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:45.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:45.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:45.895: INFO:
Jan 6 10:26:47.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:47.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:47.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:47.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Jan 6 10:26:47.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:47.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:47.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:47.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:47.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:47.895: INFO:
Jan 6 10:26:49.902: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:49.902: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:49.902: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:49.902: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Jan 6 10:26:49.902: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:49.902: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:49.902: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:49.902: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:49.902: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:49.902: INFO:
Jan 6 10:26:51.903: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:51.903: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:51.903: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:51.903: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Jan 6 10:26:51.903: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:51.903: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:51.903: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:51.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:51.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:51.904: INFO:
Jan 6 10:26:53.896: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:53.896: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:53.896: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:53.896: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Jan 6 10:26:53.896: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:53.896: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:53.896: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:53.896: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:53.896: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:53.896: INFO:
Jan 6 10:26:55.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:55.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:55.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:55.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Jan 6 10:26:55.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:55.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:55.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:55.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:55.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:55.900: INFO:
Jan 6 10:26:57.908: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:57.908: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:57.908: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:57.908: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Jan 6 10:26:57.908: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:57.908: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:57.908: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:57.908: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:57.908: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:57.908: INFO:
Jan 6 10:26:59.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:59.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:59.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:26:59.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Jan 6 10:26:59.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:26:59.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:26:59.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:26:59.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:59.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:26:59.898: INFO:
Jan 6 10:27:01.916: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:01.916: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:01.916: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:01.916: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Jan 6 10:27:01.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:01.916: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:01.916: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:01.916: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:01.916: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:01.916: INFO:
Jan 6 10:27:03.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:03.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:03.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:03.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Jan 6 10:27:03.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:03.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:03.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:03.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:03.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:03.900: INFO:
Jan 6 10:27:05.906: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:05.906: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:05.906: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:05.906: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Jan 6 10:27:05.906: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:05.906: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:05.906: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:05.906: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:05.906: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:05.906: INFO:
Jan 6 10:27:07.916: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:07.916: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:07.916: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:07.916: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Jan 6 10:27:07.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:07.916: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:07.916: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:07.916: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:07.916: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:07.916: INFO:
Jan 6 10:27:09.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:09.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:09.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:09.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Jan 6 10:27:09.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:09.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:09.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:09.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:09.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:09.900: INFO:
Jan 6 10:27:11.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:11.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:11.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:11.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Jan 6 10:27:11.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:11.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:11.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:11.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:11.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:11.900: INFO:
Jan 6 10:27:14.092: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:14.092: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:14.092: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:14.092: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (577 seconds elapsed)
Jan 6 10:27:14.092: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:14.092: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:14.092: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:14.092: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:14.092: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:14.092: INFO:
Jan 6 10:27:15.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:15.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:15.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:15.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Jan 6 10:27:15.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:15.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:15.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:15.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:15.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:15.898: INFO:
Jan 6 10:27:17.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:17.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:17.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:17.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Jan 6 10:27:17.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:17.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:17.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:17.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:17.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:17.901: INFO:
Jan 6 10:27:19.897: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:19.897: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:19.897: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:19.897: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Jan 6 10:27:19.897: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:19.897: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:19.897: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:19.897: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:19.897: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:19.897: INFO:
Jan 6 10:27:21.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:21.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:21.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:21.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Jan 6 10:27:21.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:21.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:21.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:21.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:21.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:21.904: INFO:
Jan 6 10:27:23.895: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:23.895: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:23.895: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:23.895: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Jan 6 10:27:23.895: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:23.895: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:23.895: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:23.895: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:23.895: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:23.895: INFO:
Jan 6 10:27:25.900: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:25.900: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:25.900: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:25.900: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Jan 6 10:27:25.900: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:25.900: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:25.900: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:25.900: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:25.900: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:25.900: INFO:
Jan 6 10:27:27.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:27.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:27.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:27.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Jan 6 10:27:27.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:27.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:27.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:27.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:27.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:27.898: INFO:
Jan 6 10:27:29.904: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:29.904: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:29.904: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:29.904: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Jan 6 10:27:29.904: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:29.904: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:29.904: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:29.904: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:29.904: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:29.904: INFO:
Jan 6 10:27:31.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:31.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:31.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:31.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Jan 6 10:27:31.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:31.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:31.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:31.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:31.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:31.901: INFO:
Jan 6 10:27:33.898: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:33.898: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:33.898: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:33.898: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Jan 6 10:27:33.898: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:33.898: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:33.898: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:33.898: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:33.898: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:33.898: INFO:
Jan 6 10:27:35.901: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:35.901: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:35.901: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:35.901: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Jan 6 10:27:35.901: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:35.901: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:35.901: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:35.901: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:35.901: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:35.901: INFO:
Jan 6 10:27:37.899: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:37.899: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:37.899: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:37.899: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 6 10:27:37.899: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:37.899: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:37.899: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:37.899: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:37.899: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:37.899: INFO:
Jan 6 10:27:38.324: INFO: The status of Pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:38.324: INFO: The status of Pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:38.324: INFO: The status of Pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 6 10:27:38.324: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (601 seconds elapsed)
Jan 6 10:27:38.324: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 6 10:27:38.324: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:38.324: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:38.324: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:38.324: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:38.324: INFO:
STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/06/23 10:27:38.324
STEP: Found 96 events. - test/e2e/framework/debug/dump.go:46 @ 01/06/23 10:27:38.476
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:14:56 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-n0e3dg-control-plane-crz5v_37a2aa2d-a959-40d1-bd36-c8a13cee448c became leader
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:14:57 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-n0e3dg-control-plane-crz5v_b04095ae-df17-484a-979c-97df45897a3e became leader
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:01 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:02 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-5lp5q
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:02 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-7psx9
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:02 +0000 UTC - event for coredns-56f4c55bf9-5lp5q: {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 6 10:27:38.476: INFO: At 2023-01-06 10:15:02 +0000 UTC - event for coredns-56f4c55bf9-7psx9: {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 6 10:27:38.476: INFO: At 2023-01-06 10:15:02 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-nwddn
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:02 +0000 UTC - event for kube-proxy-nwddn: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-nwddn to capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:03 +0000 UTC - event for kube-proxy-nwddn: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:07 +0000 UTC - event for kube-proxy-nwddn: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container kube-proxy
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:07 +0000 UTC - event for kube-proxy-nwddn: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container kube-proxy
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:07 +0000 UTC - event for kube-proxy-nwddn: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6" in 4.513272372s (4.513292372s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:23 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:23 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-l76v7
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:23 +0000 UTC - event for metrics-server-c9574f845-l76v7: {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 6 10:27:38.476: INFO: At 2023-01-06 10:15:25 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:25 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-x5wjl
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:25 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {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 6 10:27:38.476: INFO: At 2023-01-06 10:15:25 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-n4qb4
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:25 +0000 UTC - event for calico-node-n4qb4: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-n4qb4 to capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:26 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:35 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 9.461018544s (9.461049944s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:36 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container upgrade-ipam
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:36 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container upgrade-ipam
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:38 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container install-cni
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:38 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:38 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container install-cni
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {kubelet capz-conf-n0e3dg-control-plane-crz5v} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "bf03e0ca37ed01767d170808caf3d156a159863dc614f6215c31d22822580af0": 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 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-x5wjl to capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for coredns-56f4c55bf9-5lp5q: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-5lp5q to capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for coredns-56f4c55bf9-5lp5q: {kubelet capz-conf-n0e3dg-control-plane-crz5v} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "e7317e2267749376539544a00b6b17f2ab594266aae4acdb2356e46078bf1493": 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 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for coredns-56f4c55bf9-7psx9: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-7psx9 to capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for metrics-server-c9574f845-l76v7: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-l76v7 to capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:41 +0000 UTC - event for metrics-server-c9574f845-l76v7: {kubelet capz-conf-n0e3dg-control-plane-crz5v} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c5d7ba496b7a479f303e44bdae790ca45c0c5a0880dfefe81cbde1c32b49577e": 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 6 10:27:38.476: INFO: At 2023-01-06 10:15:42 +0000 UTC - event for coredns-56f4c55bf9-7psx9: {kubelet capz-conf-n0e3dg-control-plane-crz5v} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "cf0e74f0a3b7542b798ed02383141453d8bf1d8eae353095e17fdce978cf8adc": 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 6 10:27:38.476: INFO: At 2023-01-06 10:15:51 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} 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 6 10:27:38.476: INFO: At 2023-01-06 10:15:51 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container calico-node
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:51 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container calico-node
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:51 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.644730828s (9.644739328s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:52 +0000 UTC - event for calico-node-n4qb4: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:53 +0000 UTC - event for metrics-server-c9574f845-l76v7: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:54 +0000 UTC - event for coredns-56f4c55bf9-5lp5q: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container coredns
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:54 +0000 UTC - event for coredns-56f4c55bf9-5lp5q: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:55 +0000 UTC - event for coredns-56f4c55bf9-5lp5q: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container coredns
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:56 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:58 +0000 UTC - event for coredns-56f4c55bf9-7psx9: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container coredns
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:58 +0000 UTC - event for coredns-56f4c55bf9-7psx9: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container coredns
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:15:58 +0000 UTC - event for coredns-56f4c55bf9-7psx9: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:00 +0000 UTC - event for metrics-server-c9574f845-l76v7: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 7.091941938s (7.092079238s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:00 +0000 UTC - event for metrics-server-c9574f845-l76v7: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container metrics-server
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:01 +0000 UTC - event for metrics-server-c9574f845-l76v7: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container metrics-server
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:08 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Created: Created container calico-kube-controllers
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:08 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 7.788495126s (11.947257476s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:09 +0000 UTC - event for calico-kube-controllers-657b584867-x5wjl: {kubelet capz-conf-n0e3dg-control-plane-crz5v} Started: Started container calico-kube-controllers
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:55 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-k2xzt
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:55 +0000 UTC - event for calico-node-k2xzt: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-k2xzt to capz-conf-n0e3dg-md-0-gkfmr
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:55 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-r8g7x
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:16:55 +0000 UTC - event for kube-proxy-r8g7x: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-r8g7x to capz-conf-n0e3dg-md-0-gkfmr
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:06 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-89tz8
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:06 +0000 UTC - event for calico-node-89tz8: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-89tz8 to capz-conf-n0e3dg-md-0-ztsnc
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:06 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-f48jh
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:06 +0000 UTC - event for kube-proxy-f48jh: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-f48jh to capz-conf-n0e3dg-md-0-ztsnc
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:07 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:07 +0000 UTC - event for kube-proxy-r8g7x: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:14 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.985252774s (6.985386071s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:14 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Created: Created container upgrade-ipam
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:14 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Started: Started container upgrade-ipam
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:16 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:17 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Started: Started container install-cni
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:17 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Created: Created container install-cni
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:19 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:19 +0000 UTC - event for kube-proxy-f48jh: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:23 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:23 +0000 UTC - event for kube-proxy-r8g7x: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6" in 9.018810641s (15.998174088s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:23 +0000 UTC - event for kube-proxy-r8g7x: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Created: Created container kube-proxy
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:23 +0000 UTC - event for kube-proxy-r8g7x: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Started: Started container kube-proxy
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:26 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Started: Started container upgrade-ipam
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:26 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Created: Created container upgrade-ipam
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:26 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.227644546s (7.227820557s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:29 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Started: Started container install-cni
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:29 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Created: Created container install-cni
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:29 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:32 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 8.283094127s (8.283115726s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:32 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Created: Created container calico-node
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:32 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} Started: Started container calico-node
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:32 +0000 UTC - event for kube-proxy-f48jh: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6" in 6.477350482s (13.699313177s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:33 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:33 +0000 UTC - event for calico-node-k2xzt: {kubelet capz-conf-n0e3dg-md-0-gkfmr} 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 6 10:27:38.476: INFO: At 2023-01-06 10:17:33 +0000 UTC - event for kube-proxy-f48jh: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Started: Started container kube-proxy
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:33 +0000 UTC - event for kube-proxy-f48jh: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Created: Created container kube-proxy
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:41 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Started: Started container calico-node
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:41 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Created: Created container calico-node
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:41 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.348113988s (7.348119588s including waiting)
Jan 6 10:27:38.476: INFO: At 2023-01-06 10:17:41 +0000 UTC - event for calico-node-89tz8: {kubelet capz-conf-n0e3dg-md-0-ztsnc} 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 6 10:27:38.641: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 6 10:27:38.641: INFO: calico-kube-controllers-657b584867-x5wjl capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:16:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:16:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC }]
Jan 6 10:27:38.641: INFO: calico-node-89tz8 capz-conf-n0e3dg-md-0-ztsnc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:33 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:06 +0000 UTC }]
Jan 6 10:27:38.641: INFO: calico-node-k2xzt capz-conf-n0e3dg-md-0-gkfmr Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:23 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:34 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:34 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:16:55 +0000 UTC }]
Jan 6 10:27:38.641: INFO: calico-node-n4qb4 capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:25 +0000 UTC }]
Jan 6 10:27:38.641: INFO: coredns-56f4c55bf9-5lp5q capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:55 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:55 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC }]
Jan 6 10:27:38.641: INFO: coredns-56f4c55bf9-7psx9 capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:58 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:58 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC }]
Jan 6 10:27:38.641: INFO: etcd-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:04 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:04 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:57 +0000 UTC }]
Jan 6 10:27:38.641: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
Jan 6 10:27:38.641: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-controller-manager]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:38.641: INFO: kube-proxy-f48jh capz-conf-n0e3dg-md-0-ztsnc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:33 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:06 +0000 UTC }]
Jan 6 10:27:38.641: INFO: kube-proxy-nwddn capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:02 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:08 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:08 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:02 +0000 UTC }]
Jan 6 10:27:38.641: INFO: kube-proxy-r8g7x capz-conf-n0e3dg-md-0-gkfmr Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:17:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:16:55 +0000 UTC }]
Jan 6 10:27:38.641: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:14:35 +0000 UTC }]
Jan 6 10:27:38.641: INFO: metrics-server-c9574f845-l76v7 capz-conf-n0e3dg-control-plane-crz5v Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:16:21 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:16:21 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-06 10:15:41 +0000 UTC }]
Jan 6 10:27:38.641: INFO:
Jan 6 10:27:39.336: INFO:
Logging node info for node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:39.443: INFO: Node Info: &Node{ObjectMeta:{capz-conf-n0e3dg-control-plane-crz5v 8eec7bb6-9a1e-4496-a2ce-96e1c8b13508 1746 0 2023-01-06 10:14:52 +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:northeurope failure-domain.beta.kubernetes.io/zone:northeurope-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-n0e3dg-control-plane-crz5v 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:northeurope topology.kubernetes.io/zone:northeurope-2] map[cluster.x-k8s.io/cluster-name:capz-conf-n0e3dg cluster.x-k8s.io/cluster-namespace:capz-conf-n0e3dg cluster.x-k8s.io/machine:capz-conf-n0e3dg-control-plane-kwp9k cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-n0e3dg-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.25.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-06 10:14:52 +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-06 10:14:55 +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-06 10:15:19 +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-06 10:15:41 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-06 10:15:51 +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-06 10:26:42 +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-n0e3dg/providers/Microsoft.Compute/virtualMachines/capz-conf-n0e3dg-control-plane-crz5v,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-06 10:15:51 +0000 UTC,LastTransitionTime:2023-01-06 10:15:51 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-06 10:26:42 +0000 UTC,LastTransitionTime:2023-01-06 10:14:35 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-06 10:26:42 +0000 UTC,LastTransitionTime:2023-01-06 10:14:35 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-06 10:26:42 +0000 UTC,LastTransitionTime:2023-01-06 10:14:35 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-06 10:26:42 +0000 UTC,LastTransitionTime:2023-01-06 10:15:41 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-n0e3dg-control-plane-crz5v,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c1c0a6e66dd54c9892396f5f2e812ba5,SystemUUID:40eae93d-bbea-004b-9227-caee0df59247,BootID:385d112f-a62f-4ebc-823e-6388b7c94203,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.812+b819f8b1aa92a6,KubeProxyVersion:v1.27.0-alpha.0.812+b819f8b1aa92a6,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:e75d129fc034397c33135b63165111e130e4b32933ff6332595e20b50330c3b8 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.792_3d67e162a03d0d],SizeBytes:35419573,},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:05ab3946261df8506ce07ba2f4df14dd857ea13b042b7a50f600161bac3858c3 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.792_3d67e162a03d0d],SizeBytes:32320746,},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:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:fbebe973ecdc7df68cb57a170ab297e7a89d3eaafbf4ba5435393d03c2f704e6 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.792_3d67e162a03d0d],SizeBytes:21543133,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:8a195699216e7912f9846408eb2e36e96c2167e0ef38bd4e6daa055be891372c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6],SizeBytes:21541436,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:f2976b744e5786704088d40867a3fdba41e45e868a96925beec84b5fab120833 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.792_3d67e162a03d0d],SizeBytes:17522568,},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: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 6 10:27:39.443: INFO:
Logging kubelet events for node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:39.549: INFO:
Logging pods the kubelet thinks is on node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:39.682: INFO: calico-node-n4qb4 started at 2023-01-06 10:15:25 +0000 UTC (2+1 container statuses recorded)
Jan 6 10:27:39.682: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 6 10:27:39.682: INFO: Init container install-cni ready: true, restart count 0
Jan 6 10:27:39.682: INFO: Container calico-node ready: true, restart count 0
Jan 6 10:27:39.682: INFO: metrics-server-c9574f845-l76v7 started at 2023-01-06 10:15:41 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:39.682: INFO: Container metrics-server ready: true, restart count 0
Jan 6 10:27:39.682: INFO: calico-kube-controllers-657b584867-x5wjl started at 2023-01-06 10:15:41 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:39.682: INFO: Container calico-kube-controllers ready: true, restart count 0
Jan 6 10:27:39.682: INFO: coredns-56f4c55bf9-7psx9 started at 2023-01-06 10:15:41 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:39.682: INFO: Container coredns ready: true, restart count 0
Jan 6 10:27:39.682: INFO: kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v started at <nil> (0+0 container statuses recorded)
Jan 6 10:27:39.683: INFO: etcd-capz-conf-n0e3dg-control-plane-crz5v started at 2023-01-06 10:14:57 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:39.683: INFO: Container etcd ready: true, restart count 0
Jan 6 10:27:39.683: INFO: kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v started at <nil> (0+0 container statuses recorded)
Jan 6 10:27:39.683: INFO: kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v started at <nil> (0+0 container statuses recorded)
Jan 6 10:27:39.683: INFO: kube-proxy-nwddn started at 2023-01-06 10:15:02 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:39.683: INFO: Container kube-proxy ready: true, restart count 0
Jan 6 10:27:39.683: INFO: coredns-56f4c55bf9-5lp5q started at 2023-01-06 10:15:41 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:39.683: INFO: Container coredns ready: true, restart count 0
Jan 6 10:27:40.126: INFO:
Latency metrics for node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:40.126: INFO:
Logging node info for node capz-conf-n0e3dg-md-0-gkfmr
Jan 6 10:27:40.231: INFO: Node Info: &Node{ObjectMeta:{capz-conf-n0e3dg-md-0-gkfmr c3ca4689-9491-4f5f-b737-d005ef5bf750 1400 0 2023-01-06 10:16:55 +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:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-n0e3dg-md-0-gkfmr kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-n0e3dg cluster.x-k8s.io/cluster-namespace:capz-conf-n0e3dg cluster.x-k8s.io/machine:capz-conf-n0e3dg-md-0-6db95bbdcd-fv925 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-n0e3dg-md-0-6db95bbdcd 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.137.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-06 10:16:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-06 10:16:55 +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":{}}} } {kube-controller-manager Update v1 2023-01-06 10:17:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2023-01-06 10:17:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2023-01-06 10:17:32 +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-06 10:22:52 +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-n0e3dg/providers/Microsoft.Compute/virtualMachines/capz-conf-n0e3dg-md-0-gkfmr,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-06 10:17:32 +0000 UTC,LastTransitionTime:2023-01-06 10:17:32 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-06 10:22:52 +0000 UTC,LastTransitionTime:2023-01-06 10:16:55 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-06 10:22:52 +0000 UTC,LastTransitionTime:2023-01-06 10:16:55 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-06 10:22:52 +0000 UTC,LastTransitionTime:2023-01-06 10:16:55 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-06 10:22:52 +0000 UTC,LastTransitionTime:2023-01-06 10:17:21 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-n0e3dg-md-0-gkfmr,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:8f5cd55a6cd84b2c9cd20a4399183c66,SystemUUID:87ece18e-9e24-3a46-993a-30a6556fb061,BootID:a34f94ee-5627-4c76-9432-b6b71614e3ea,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.812+b819f8b1aa92a6,KubeProxyVersion:v1.27.0-alpha.0.812+b819f8b1aa92a6,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:[capzci.azurecr.io/kube-proxy@sha256:8a195699216e7912f9846408eb2e36e96c2167e0ef38bd4e6daa055be891372c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6],SizeBytes:21541436,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},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 6 10:27:40.232: INFO:
Logging kubelet events for node capz-conf-n0e3dg-md-0-gkfmr
Jan 6 10:27:40.343: INFO:
Logging pods the kubelet thinks is on node capz-conf-n0e3dg-md-0-gkfmr
Jan 6 10:27:40.457: INFO: calico-node-k2xzt started at 2023-01-06 10:17:01 +0000 UTC (2+1 container statuses recorded)
Jan 6 10:27:40.457: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 6 10:27:40.457: INFO: Init container install-cni ready: true, restart count 0
Jan 6 10:27:40.457: INFO: Container calico-node ready: true, restart count 0
Jan 6 10:27:40.457: INFO: kube-proxy-r8g7x started at 2023-01-06 10:17:01 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:40.457: INFO: Container kube-proxy ready: true, restart count 0
Jan 6 10:27:40.862: INFO:
Latency metrics for node capz-conf-n0e3dg-md-0-gkfmr
Jan 6 10:27:40.862: INFO:
Logging node info for node capz-conf-n0e3dg-md-0-ztsnc
Jan 6 10:27:40.968: INFO: Node Info: &Node{ObjectMeta:{capz-conf-n0e3dg-md-0-ztsnc 96175790-f9f4-458e-a002-3abbd223d27f 1415 0 2023-01-06 10:17:06 +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:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-n0e3dg-md-0-ztsnc kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-n0e3dg cluster.x-k8s.io/cluster-namespace:capz-conf-n0e3dg cluster.x-k8s.io/machine:capz-conf-n0e3dg-md-0-6db95bbdcd-rs67z cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-n0e3dg-md-0-6db95bbdcd 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.72.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-06 10:17:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-06 10:17:06 +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-06 10:17:25 +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-06 10:17:32 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-06 10:17:41 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-06 10:23:01 +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-n0e3dg/providers/Microsoft.Compute/virtualMachines/capz-conf-n0e3dg-md-0-ztsnc,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-06 10:17:41 +0000 UTC,LastTransitionTime:2023-01-06 10:17:41 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-06 10:23:01 +0000 UTC,LastTransitionTime:2023-01-06 10:17:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-06 10:23:01 +0000 UTC,LastTransitionTime:2023-01-06 10:17:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-06 10:23:01 +0000 UTC,LastTransitionTime:2023-01-06 10:17:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-06 10:23:01 +0000 UTC,LastTransitionTime:2023-01-06 10:17:32 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-n0e3dg-md-0-ztsnc,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:b7bf250e1579473e8121757d38855717,SystemUUID:3f720a9a-bdce-d44d-9347-5dc5fd8e8cd6,BootID:2cec36de-d200-4698-a56f-45505f830c61,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.812+b819f8b1aa92a6,KubeProxyVersion:v1.27.0-alpha.0.812+b819f8b1aa92a6,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:[capzci.azurecr.io/kube-proxy@sha256:8a195699216e7912f9846408eb2e36e96c2167e0ef38bd4e6daa055be891372c capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.812_b819f8b1aa92a6],SizeBytes:21541436,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},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 6 10:27:40.968: INFO:
Logging kubelet events for node capz-conf-n0e3dg-md-0-ztsnc
Jan 6 10:27:41.074: INFO:
Logging pods the kubelet thinks is on node capz-conf-n0e3dg-md-0-ztsnc
Jan 6 10:27:41.189: INFO: calico-node-89tz8 started at 2023-01-06 10:17:15 +0000 UTC (2+1 container statuses recorded)
Jan 6 10:27:41.189: INFO: Init container upgrade-ipam ready: true, restart count 0
Jan 6 10:27:41.189: INFO: Init container install-cni ready: true, restart count 0
Jan 6 10:27:41.189: INFO: Container calico-node ready: true, restart count 0
Jan 6 10:27:41.189: INFO: kube-proxy-f48jh started at 2023-01-06 10:17:15 +0000 UTC (0+1 container statuses recorded)
Jan 6 10:27:41.189: INFO: Container kube-proxy ready: true, restart count 0
Jan 6 10:27:41.706: INFO:
Latency metrics for node capz-conf-n0e3dg-md-0-ztsnc
Jan 6 10:27:41.926: INFO: Running kubectl logs on non-ready containers in kube-system
Jan 6 10:27:42.268: INFO: Failed to get logs of pod kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v)
Jan 6 10:27:42.268: INFO: Logs of kube-system/kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v:kube-apiserver on node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:42.268: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-n0e3dg-control-plane-crz5v:kube-apiserver
Jan 6 10:27:42.668: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v)
Jan 6 10:27:42.668: INFO: Logs of kube-system/kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v:kube-controller-manager on node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:42.668: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v:kube-controller-manager
Jan 6 10:27:43.068: INFO: Failed to get logs of pod kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v)
Jan 6 10:27:43.068: INFO: Logs of kube-system/kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v:kube-scheduler on node capz-conf-n0e3dg-control-plane-crz5v
Jan 6 10:27:43.068: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v: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-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Pending []
kube-controller-manager-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-controller-manager]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-controller-manager]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason: Message:}]
kube-scheduler-capz-conf-n0e3dg-control-plane-crz5v capz-conf-n0e3dg-control-plane-crz5v Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-06 10:14:35 +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-06 10:14:35 +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-06 10:14:35 +0000 UTC Reason: Message:}]
In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:249 @ 01/06/23 10:27:43.069
< Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/06/23 10:27:43.069 (10m6.589s)
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/06/23 10:27:43.124from 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/06/23 10:27:43.124
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/06/23 10:27:43.124from 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/06/23 10:27:43.124
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/06/23 10:27:43.122from 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/06/23 10:27:43.122
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/06/23 10:27:43.121from 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/06/23 10:27:43.121
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
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/06/23 10:27:43.125from 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/06/23 10:27:43.125
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
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