PR #115040 pull-kubernetes-e2e-capz-conformance #1615005552440512512
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | mpatlasov: Stop reporting volume limits for migrated in-tree drivers in Node object |
| Result | SUCCESS |
| Tests | 25 failed / 30 succeeded |
| Started | |
| Elapsed | 53m20s |
| Revision | 5e427ae6c92ce0f09b3b77fff59a009192aa3c36 |
| Refs |
115040 |
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/16/23 16:07:49.246from 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/16/23 16:07:49.246
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/16/23 16:07:49.244from 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/16/23 16:07:49.244
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/16/23 16:07:49.247from 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/16/23 16:07:49.247
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/16/23 16:07:49.262from 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/16/23 16:07:49.262
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/16/23 16:07:49.262from 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/16/23 16:07:49.262
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/16/23 16:07:49.245from 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/16/23 16:07:49.245
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/16/23 16:07:49.245from 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/16/23 16:07:49.245
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/16/23 16:07:49.243from 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/16/23 16:07:49.243
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/16/23 16:07:49.244from 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/16/23 16:07:49.244
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/16/23 16:07:49.245from 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/16/23 16:07:49.245
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/16/23 16:07:49.246from 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/16/23 16:07:49.246
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/16/23 16:07:49.243from 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/16/23 16:07:49.243
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/16/23 16:07:49.246from 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/16/23 16:07:49.246
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-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:06 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:38 +0000 UTC Reason: Message:} {Type:ContainersReady Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:33 +0000 UTC Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:06 +0000 UTC Reason: Message:}]
kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/16/23 16:07:49.147
> Enter [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/16/23 15:57:11.446
Jan 16 15:57:11.447: INFO: >>> kubeConfig: /tmp/kubeconfig
Jan 16 15:57:11.449: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Jan 16 15:57:11.670: INFO: Condition Ready of node capz-conf-g30srl-md-0-k26sq is true, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoExecute 2023-01-16 15:56:43 +0000 UTC}]. Failure
Jan 16 15:57:11.670: INFO: Condition Ready of node capz-conf-g30srl-md-0-zcjwc is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-16 15:56:53 +0000 UTC}]. Failure
Jan 16 15:57:11.670: INFO: Unschedulable nodes= 2, maximum value for starting tests= 0
Jan 16 15:57:11.670: INFO: -> Node capz-conf-g30srl-md-0-k26sq [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready NoExecute 2023-01-16 15:56:43 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
Jan 16 15:57:11.670: INFO: -> Node capz-conf-g30srl-md-0-zcjwc [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-16 15:56:53 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
Jan 16 15:57:11.670: INFO: ==== node wait: 1 out of 3 nodes are ready, max notReady allowed 0. Need 2 more before starting.
Jan 16 15:57:41.718: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Jan 16 15:57:41.911: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:41.911: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:41.911: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:41.911: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Jan 16 15:57:41.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:41.911: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:41.911: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:41.911: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:41.911: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:41.911: INFO:
Jan 16 15:57:44.052: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:44.052: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:44.052: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:44.052: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Jan 16 15:57:44.052: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:44.052: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:44.052: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:44.052: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:44.052: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:44.052: INFO:
Jan 16 15:57:46.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:46.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:46.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:46.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Jan 16 15:57:46.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:46.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:46.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:46.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:46.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:46.037: INFO:
Jan 16 15:57:48.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:48.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:48.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:48.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Jan 16 15:57:48.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:48.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:48.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:48.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:48.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:48.033: INFO:
Jan 16 15:57:50.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:50.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:50.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:50.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Jan 16 15:57:50.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:50.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:50.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:50.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:50.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:50.033: INFO:
Jan 16 15:57:52.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:52.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:52.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:52.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Jan 16 15:57:52.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:52.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:52.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:52.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:52.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:52.036: INFO:
Jan 16 15:57:54.041: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:54.041: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:54.041: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:54.041: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Jan 16 15:57:54.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:54.041: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:54.041: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:54.041: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:54.041: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:54.041: INFO:
Jan 16 15:57:56.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:56.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:56.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:56.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Jan 16 15:57:56.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:56.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:56.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:56.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:56.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:56.033: INFO:
Jan 16 15:57:58.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:58.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:58.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:57:58.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Jan 16 15:57:58.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:57:58.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:57:58.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:57:58.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:58.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:57:58.037: INFO:
Jan 16 15:58:00.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:00.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:00.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:00.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Jan 16 15:58:00.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:00.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:00.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:00.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:00.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:00.037: INFO:
Jan 16 15:58:02.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:02.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:02.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:02.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Jan 16 15:58:02.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:02.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:02.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:02.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:02.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:02.035: INFO:
Jan 16 15:58:04.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:04.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:04.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:04.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Jan 16 15:58:04.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:04.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:04.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:04.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:04.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:04.032: INFO:
Jan 16 15:58:06.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:06.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:06.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:06.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Jan 16 15:58:06.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:06.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:06.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:06.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:06.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:06.035: INFO:
Jan 16 15:58:08.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:08.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:08.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:08.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Jan 16 15:58:08.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:08.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:08.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:08.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:08.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:08.037: INFO:
Jan 16 15:58:10.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:10.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:10.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:10.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Jan 16 15:58:10.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:10.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:10.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:10.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:10.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:10.031: INFO:
Jan 16 15:58:12.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:12.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:12.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:12.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Jan 16 15:58:12.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:12.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:12.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:12.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:12.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:12.032: INFO:
Jan 16 15:58:14.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:14.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:14.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:14.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Jan 16 15:58:14.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:14.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:14.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:14.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:14.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:14.031: INFO:
Jan 16 15:58:16.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:16.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:16.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:16.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Jan 16 15:58:16.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:16.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:16.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:16.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:16.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:16.035: INFO:
Jan 16 15:58:18.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:18.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:18.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:18.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Jan 16 15:58:18.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:18.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:18.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:18.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:18.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:18.037: INFO:
Jan 16 15:58:20.055: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:20.055: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:20.055: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:20.055: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Jan 16 15:58:20.055: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:20.055: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:20.055: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:20.055: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:20.055: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:20.055: INFO:
Jan 16 15:58:22.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:22.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:22.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:22.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Jan 16 15:58:22.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:22.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:22.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:22.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:22.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:22.035: INFO:
Jan 16 15:58:24.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:24.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:24.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:24.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Jan 16 15:58:24.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:24.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:24.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:24.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:24.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:24.032: INFO:
Jan 16 15:58:26.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:26.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:26.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:26.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Jan 16 15:58:26.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:26.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:26.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:26.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:26.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:26.036: INFO:
Jan 16 15:58:28.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:28.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:28.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:28.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Jan 16 15:58:28.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:28.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:28.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:28.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:28.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:28.034: INFO:
Jan 16 15:58:30.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:30.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:30.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:30.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Jan 16 15:58:30.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:30.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:30.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:30.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:30.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:30.037: INFO:
Jan 16 15:58:32.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:32.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:32.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:32.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Jan 16 15:58:32.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:32.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:32.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:32.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:32.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:32.029: INFO:
Jan 16 15:58:34.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:34.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:34.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:34.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Jan 16 15:58:34.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:34.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:34.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:34.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:34.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:34.033: INFO:
Jan 16 15:58:36.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:36.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:36.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:36.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Jan 16 15:58:36.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:36.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:36.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:36.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:36.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:36.036: INFO:
Jan 16 15:58:38.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:38.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:38.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:38.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Jan 16 15:58:38.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:38.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:38.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:38.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:38.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:38.034: INFO:
Jan 16 15:58:40.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:40.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:40.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:40.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Jan 16 15:58:40.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:40.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:40.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:40.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:40.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:40.032: INFO:
Jan 16 15:58:42.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:42.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:42.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:42.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Jan 16 15:58:42.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:42.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:42.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:42.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:42.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:42.033: INFO:
Jan 16 15:58:44.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:44.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:44.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:44.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Jan 16 15:58:44.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:44.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:44.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:44.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:44.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:44.030: INFO:
Jan 16 15:58:46.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:46.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:46.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:46.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Jan 16 15:58:46.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:46.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:46.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:46.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:46.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:46.031: INFO:
Jan 16 15:58:48.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:48.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:48.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:48.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Jan 16 15:58:48.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:48.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:48.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:48.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:48.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:48.030: INFO:
Jan 16 15:58:50.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:50.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:50.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:50.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Jan 16 15:58:50.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:50.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:50.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:50.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:50.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:50.030: INFO:
Jan 16 15:58:52.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:52.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:52.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:52.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Jan 16 15:58:52.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:52.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:52.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:52.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:52.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:52.032: INFO:
Jan 16 15:58:54.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:54.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:54.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:54.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Jan 16 15:58:54.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:54.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:54.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:54.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:54.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:54.032: INFO:
Jan 16 15:58:56.045: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:56.045: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:56.045: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:56.045: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Jan 16 15:58:56.045: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:56.045: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:56.045: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:56.045: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:56.045: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:56.045: INFO:
Jan 16 15:58:58.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:58.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:58.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:58:58.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Jan 16 15:58:58.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:58:58.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:58:58.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:58:58.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:58.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:58:58.033: INFO:
Jan 16 15:59:00.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:00.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:00.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:00.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Jan 16 15:59:00.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:00.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:00.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:00.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:00.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:00.032: INFO:
Jan 16 15:59:02.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:02.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:02.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:02.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Jan 16 15:59:02.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:02.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:02.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:02.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:02.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:02.032: INFO:
Jan 16 15:59:04.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:04.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:04.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:04.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Jan 16 15:59:04.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:04.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:04.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:04.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:04.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:04.035: INFO:
Jan 16 15:59:06.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:06.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:06.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:06.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Jan 16 15:59:06.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:06.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:06.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:06.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:06.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:06.037: INFO:
Jan 16 15:59:08.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:08.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:08.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:08.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Jan 16 15:59:08.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:08.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:08.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:08.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:08.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:08.030: INFO:
Jan 16 15:59:10.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:10.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:10.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:10.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Jan 16 15:59:10.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:10.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:10.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:10.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:10.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:10.032: INFO:
Jan 16 15:59:12.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:12.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:12.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:12.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Jan 16 15:59:12.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:12.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:12.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:12.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:12.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:12.031: INFO:
Jan 16 15:59:14.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:14.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:14.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:14.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Jan 16 15:59:14.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:14.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:14.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:14.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:14.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:14.038: INFO:
Jan 16 15:59:16.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:16.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:16.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:16.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Jan 16 15:59:16.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:16.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:16.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:16.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:16.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:16.032: INFO:
Jan 16 15:59:18.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:18.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:18.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:18.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Jan 16 15:59:18.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:18.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:18.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:18.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:18.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:18.032: INFO:
Jan 16 15:59:20.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:20.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:20.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:20.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Jan 16 15:59:20.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:20.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:20.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:20.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:20.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:20.036: INFO:
Jan 16 15:59:22.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:22.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:22.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:22.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Jan 16 15:59:22.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:22.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:22.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:22.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:22.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:22.033: INFO:
Jan 16 15:59:24.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:24.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:24.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:24.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Jan 16 15:59:24.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:24.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:24.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:24.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:24.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:24.031: INFO:
Jan 16 15:59:26.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:26.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:26.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:26.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Jan 16 15:59:26.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:26.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:26.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:26.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:26.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:26.031: INFO:
Jan 16 15:59:28.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:28.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:28.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:28.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Jan 16 15:59:28.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:28.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:28.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:28.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:28.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:28.033: INFO:
Jan 16 15:59:30.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:30.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:30.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:30.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Jan 16 15:59:30.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:30.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:30.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:30.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:30.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:30.031: INFO:
Jan 16 15:59:32.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:32.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:32.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:32.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Jan 16 15:59:32.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:32.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:32.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:32.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:32.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:32.033: INFO:
Jan 16 15:59:34.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:34.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:34.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:34.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Jan 16 15:59:34.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:34.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:34.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:34.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:34.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:34.032: INFO:
Jan 16 15:59:36.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:36.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:36.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:36.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Jan 16 15:59:36.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:36.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:36.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:36.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:36.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:36.032: INFO:
Jan 16 15:59:38.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:38.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:38.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:38.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Jan 16 15:59:38.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:38.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:38.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:38.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:38.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:38.032: INFO:
Jan 16 15:59:40.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:40.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:40.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:40.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Jan 16 15:59:40.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:40.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:40.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:40.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:40.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:40.030: INFO:
Jan 16 15:59:42.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:42.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:42.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:42.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Jan 16 15:59:42.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:42.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:42.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:42.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:42.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:42.031: INFO:
Jan 16 15:59:44.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:44.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:44.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:44.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Jan 16 15:59:44.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:44.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:44.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:44.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:44.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:44.030: INFO:
Jan 16 15:59:46.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:46.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:46.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:46.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Jan 16 15:59:46.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:46.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:46.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:46.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:46.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:46.032: INFO:
Jan 16 15:59:48.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:48.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:48.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:48.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Jan 16 15:59:48.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:48.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:48.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:48.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:48.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:48.040: INFO:
Jan 16 15:59:50.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:50.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:50.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:50.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Jan 16 15:59:50.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:50.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:50.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:50.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:50.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:50.039: INFO:
Jan 16 15:59:52.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:52.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:52.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:52.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Jan 16 15:59:52.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:52.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:52.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:52.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:52.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:52.030: INFO:
Jan 16 15:59:54.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:54.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:54.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:54.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Jan 16 15:59:54.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:54.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:54.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:54.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:54.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:54.030: INFO:
Jan 16 15:59:56.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:56.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:56.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:56.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Jan 16 15:59:56.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:56.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:56.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:56.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:56.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:56.038: INFO:
Jan 16 15:59:58.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:58.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:58.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 15:59:58.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Jan 16 15:59:58.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 15:59:58.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 15:59:58.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 15:59:58.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:58.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 15:59:58.034: INFO:
Jan 16 16:00:00.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:00.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:00.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:00.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Jan 16 16:00:00.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:00.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:00.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:00.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:00.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:00.031: INFO:
Jan 16 16:00:02.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:02.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:02.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:02.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Jan 16 16:00:02.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:02.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:02.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:02.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:02.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:02.030: INFO:
Jan 16 16:00:04.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:04.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:04.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:04.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Jan 16 16:00:04.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:04.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:04.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:04.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:04.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:04.033: INFO:
Jan 16 16:00:06.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:06.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:06.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:06.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Jan 16 16:00:06.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:06.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:06.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:06.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:06.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:06.033: INFO:
Jan 16 16:00:08.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:08.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:08.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:08.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Jan 16 16:00:08.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:08.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:08.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:08.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:08.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:08.038: INFO:
Jan 16 16:00:10.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:10.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:10.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:10.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Jan 16 16:00:10.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:10.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:10.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:10.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:10.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:10.030: INFO:
Jan 16 16:00:12.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:12.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:12.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:12.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Jan 16 16:00:12.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:12.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:12.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:12.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:12.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:12.030: INFO:
Jan 16 16:00:14.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:14.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:14.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:14.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Jan 16 16:00:14.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:14.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:14.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:14.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:14.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:14.031: INFO:
Jan 16 16:00:16.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:16.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:16.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:16.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Jan 16 16:00:16.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:16.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:16.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:16.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:16.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:16.035: INFO:
Jan 16 16:00:18.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:18.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:18.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:18.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Jan 16 16:00:18.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:18.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:18.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:18.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:18.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:18.032: INFO:
Jan 16 16:00:20.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:20.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:20.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:20.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Jan 16 16:00:20.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:20.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:20.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:20.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:20.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:20.030: INFO:
Jan 16 16:00:22.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:22.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:22.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:22.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Jan 16 16:00:22.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:22.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:22.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:22.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:22.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:22.030: INFO:
Jan 16 16:00:24.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:24.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:24.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:24.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Jan 16 16:00:24.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:24.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:24.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:24.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:24.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:24.031: INFO:
Jan 16 16:00:26.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:26.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:26.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:26.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Jan 16 16:00:26.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:26.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:26.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:26.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:26.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:26.035: INFO:
Jan 16 16:00:28.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:28.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:28.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:28.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Jan 16 16:00:28.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:28.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:28.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:28.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:28.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:28.032: INFO:
Jan 16 16:00:30.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:30.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:30.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:30.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Jan 16 16:00:30.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:30.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:30.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:30.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:30.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:30.031: INFO:
Jan 16 16:00:32.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:32.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:32.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:32.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Jan 16 16:00:32.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:32.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:32.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:32.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:32.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:32.034: INFO:
Jan 16 16:00:34.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:34.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:34.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:34.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Jan 16 16:00:34.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:34.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:34.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:34.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:34.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:34.037: INFO:
Jan 16 16:00:36.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:36.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:36.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:36.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Jan 16 16:00:36.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:36.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:36.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:36.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:36.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:36.033: INFO:
Jan 16 16:00:38.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:38.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:38.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:38.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Jan 16 16:00:38.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:38.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:38.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:38.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:38.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:38.039: INFO:
Jan 16 16:00:40.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:40.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:40.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:40.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Jan 16 16:00:40.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:40.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:40.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:40.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:40.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:40.033: INFO:
Jan 16 16:00:42.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:42.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:42.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:42.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Jan 16 16:00:42.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:42.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:42.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:42.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:42.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:42.035: INFO:
Jan 16 16:00:44.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:44.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:44.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:44.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Jan 16 16:00:44.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:44.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:44.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:44.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:44.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:44.033: INFO:
Jan 16 16:00:46.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:46.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:46.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:46.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Jan 16 16:00:46.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:46.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:46.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:46.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:46.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:46.038: INFO:
Jan 16 16:00:48.049: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:48.049: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:48.049: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:48.049: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Jan 16 16:00:48.049: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:48.049: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:48.049: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:48.049: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:48.049: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:48.049: INFO:
Jan 16 16:00:50.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:50.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:50.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:50.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Jan 16 16:00:50.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:50.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:50.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:50.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:50.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:50.030: INFO:
Jan 16 16:00:52.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:52.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:52.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:52.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Jan 16 16:00:52.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:52.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:52.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:52.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:52.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:52.034: INFO:
Jan 16 16:00:54.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:54.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:54.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:54.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Jan 16 16:00:54.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:54.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:54.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:54.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:54.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:54.031: INFO:
Jan 16 16:00:56.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:56.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:56.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:56.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Jan 16 16:00:56.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:56.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:56.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:56.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:56.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:56.034: INFO:
Jan 16 16:00:58.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:58.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:58.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:00:58.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Jan 16 16:00:58.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:00:58.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:00:58.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:00:58.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:58.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:00:58.030: INFO:
Jan 16 16:01:00.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:00.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:00.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:00.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Jan 16 16:01:00.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:00.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:00.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:00.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:00.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:00.031: INFO:
Jan 16 16:01:02.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:02.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:02.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:02.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Jan 16 16:01:02.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:02.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:02.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:02.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:02.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:02.033: INFO:
Jan 16 16:01:04.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:04.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:04.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:04.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Jan 16 16:01:04.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:04.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:04.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:04.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:04.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:04.031: INFO:
Jan 16 16:01:06.044: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:06.044: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:06.044: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:06.044: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Jan 16 16:01:06.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:06.044: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:06.044: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:06.044: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:06.044: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:06.044: INFO:
Jan 16 16:01:08.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:08.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:08.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:08.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Jan 16 16:01:08.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:08.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:08.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:08.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:08.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:08.030: INFO:
Jan 16 16:01:10.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:10.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:10.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:10.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Jan 16 16:01:10.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:10.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:10.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:10.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:10.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:10.030: INFO:
Jan 16 16:01:12.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:12.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:12.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:12.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Jan 16 16:01:12.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:12.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:12.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:12.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:12.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:12.030: INFO:
Jan 16 16:01:14.041: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:14.041: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:14.041: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:14.041: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Jan 16 16:01:14.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:14.041: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:14.041: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:14.041: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:14.041: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:14.041: INFO:
Jan 16 16:01:16.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:16.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:16.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:16.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Jan 16 16:01:16.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:16.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:16.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:16.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:16.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:16.032: INFO:
Jan 16 16:01:18.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:18.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:18.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:18.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Jan 16 16:01:18.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:18.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:18.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:18.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:18.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:18.030: INFO:
Jan 16 16:01:20.048: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:20.048: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:20.048: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:20.048: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Jan 16 16:01:20.048: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:20.048: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:20.048: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:20.048: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:20.048: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:20.048: INFO:
Jan 16 16:01:22.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:22.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:22.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:22.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Jan 16 16:01:22.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:22.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:22.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:22.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:22.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:22.031: INFO:
Jan 16 16:01:24.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:24.041: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:24.041: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:24.041: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Jan 16 16:01:24.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:24.041: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:24.041: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:24.041: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:24.041: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:24.041: INFO:
Jan 16 16:01:26.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:26.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:26.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:26.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Jan 16 16:01:26.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:26.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:26.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:26.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:26.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:26.034: INFO:
Jan 16 16:01:28.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:28.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:28.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:28.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Jan 16 16:01:28.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:28.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:28.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:28.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:28.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:28.034: INFO:
Jan 16 16:01:30.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:30.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:30.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:30.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Jan 16 16:01:30.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:30.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:30.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:30.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:30.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:30.034: INFO:
Jan 16 16:01:32.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:32.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:32.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:32.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Jan 16 16:01:32.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:32.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:32.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:32.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:32.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:32.030: INFO:
Jan 16 16:01:34.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:34.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:34.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:34.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Jan 16 16:01:34.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:34.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:34.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:34.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:34.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:34.029: INFO:
Jan 16 16:01:36.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:36.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:36.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:36.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Jan 16 16:01:36.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:36.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:36.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:36.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:36.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:36.031: INFO:
Jan 16 16:01:38.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:38.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:38.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:38.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Jan 16 16:01:38.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:38.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:38.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:38.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:38.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:38.030: INFO:
Jan 16 16:01:40.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:40.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:40.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:40.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Jan 16 16:01:40.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:40.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:40.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:40.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:40.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:40.034: INFO:
Jan 16 16:01:42.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:42.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:42.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:42.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Jan 16 16:01:42.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:42.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:42.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:42.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:42.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:42.030: INFO:
Jan 16 16:01:44.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:44.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:44.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:44.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Jan 16 16:01:44.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:44.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:44.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:44.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:44.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:44.031: INFO:
Jan 16 16:01:46.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:46.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:46.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:46.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Jan 16 16:01:46.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:46.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:46.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:46.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:46.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:46.030: INFO:
Jan 16 16:01:48.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:48.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:48.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:48.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Jan 16 16:01:48.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:48.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:48.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:48.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:48.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:48.039: INFO:
Jan 16 16:01:50.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:50.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:50.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:50.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Jan 16 16:01:50.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:50.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:50.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:50.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:50.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:50.033: INFO:
Jan 16 16:01:52.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:52.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:52.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:52.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Jan 16 16:01:52.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:52.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:52.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:52.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:52.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:52.038: INFO:
Jan 16 16:01:54.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:54.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:54.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:54.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Jan 16 16:01:54.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:54.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:54.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:54.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:54.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:54.031: INFO:
Jan 16 16:01:56.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:56.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:56.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:56.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Jan 16 16:01:56.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:56.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:56.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:56.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:56.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:56.032: INFO:
Jan 16 16:01:58.041: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:58.041: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:58.041: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:01:58.041: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Jan 16 16:01:58.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:01:58.041: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:01:58.041: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:01:58.041: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:58.041: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:01:58.041: INFO:
Jan 16 16:02:00.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:00.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:00.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:00.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Jan 16 16:02:00.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:00.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:00.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:00.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:00.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:00.032: INFO:
Jan 16 16:02:02.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:02.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:02.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:02.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Jan 16 16:02:02.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:02.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:02.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:02.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:02.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:02.035: INFO:
Jan 16 16:02:04.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:04.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:04.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:04.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Jan 16 16:02:04.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:04.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:04.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:04.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:04.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:04.033: INFO:
Jan 16 16:02:06.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:06.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:06.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:06.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Jan 16 16:02:06.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:06.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:06.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:06.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:06.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:06.031: INFO:
Jan 16 16:02:08.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:08.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:08.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:08.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Jan 16 16:02:08.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:08.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:08.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:08.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:08.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:08.029: INFO:
Jan 16 16:02:10.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:10.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:10.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:10.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Jan 16 16:02:10.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:10.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:10.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:10.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:10.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:10.032: INFO:
Jan 16 16:02:12.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:12.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:12.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:12.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Jan 16 16:02:12.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:12.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:12.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:12.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:12.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:12.033: INFO:
Jan 16 16:02:14.028: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:14.028: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:14.028: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:14.028: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Jan 16 16:02:14.028: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:14.028: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:14.028: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:14.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:14.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:14.029: INFO:
Jan 16 16:02:16.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:16.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:16.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:16.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Jan 16 16:02:16.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:16.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:16.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:16.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:16.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:16.032: INFO:
Jan 16 16:02:18.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:18.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:18.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:18.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Jan 16 16:02:18.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:18.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:18.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:18.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:18.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:18.036: INFO:
Jan 16 16:02:20.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:20.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:20.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:20.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Jan 16 16:02:20.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:20.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:20.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:20.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:20.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:20.029: INFO:
Jan 16 16:02:22.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:22.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:22.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:22.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Jan 16 16:02:22.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:22.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:22.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:22.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:22.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:22.029: INFO:
Jan 16 16:02:24.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:24.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:24.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:24.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Jan 16 16:02:24.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:24.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:24.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:24.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:24.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:24.029: INFO:
Jan 16 16:02:26.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:26.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:26.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:26.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Jan 16 16:02:26.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:26.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:26.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:26.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:26.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:26.034: INFO:
Jan 16 16:02:28.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:28.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:28.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:28.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Jan 16 16:02:28.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:28.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:28.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:28.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:28.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:28.031: INFO:
Jan 16 16:02:30.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:30.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:30.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:30.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Jan 16 16:02:30.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:30.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:30.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:30.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:30.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:30.030: INFO:
Jan 16 16:02:32.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:32.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:32.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:32.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Jan 16 16:02:32.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:32.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:32.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:32.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:32.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:32.031: INFO:
Jan 16 16:02:34.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:34.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:34.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:34.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Jan 16 16:02:34.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:34.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:34.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:34.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:34.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:34.036: INFO:
Jan 16 16:02:36.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:36.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:36.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:36.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Jan 16 16:02:36.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:36.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:36.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:36.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:36.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:36.031: INFO:
Jan 16 16:02:38.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:38.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:38.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:38.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Jan 16 16:02:38.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:38.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:38.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:38.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:38.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:38.030: INFO:
Jan 16 16:02:40.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:40.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:40.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:40.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Jan 16 16:02:40.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:40.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:40.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:40.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:40.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:40.031: INFO:
Jan 16 16:02:42.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:42.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:42.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:42.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Jan 16 16:02:42.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:42.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:42.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:42.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:42.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:42.029: INFO:
Jan 16 16:02:44.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:44.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:44.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:44.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Jan 16 16:02:44.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:44.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:44.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:44.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:44.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:44.034: INFO:
Jan 16 16:02:46.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:46.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:46.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:46.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Jan 16 16:02:46.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:46.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:46.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:46.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:46.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:46.032: INFO:
Jan 16 16:02:48.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:48.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:48.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:48.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Jan 16 16:02:48.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:48.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:48.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:48.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:48.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:48.032: INFO:
Jan 16 16:02:50.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:50.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:50.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:50.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Jan 16 16:02:50.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:50.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:50.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:50.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:50.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:50.030: INFO:
Jan 16 16:02:52.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:52.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:52.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:52.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Jan 16 16:02:52.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:52.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:52.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:52.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:52.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:52.033: INFO:
Jan 16 16:02:54.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:54.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:54.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:54.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Jan 16 16:02:54.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:54.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:54.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:54.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:54.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:54.032: INFO:
Jan 16 16:02:56.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:56.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:56.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:56.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Jan 16 16:02:56.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:56.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:56.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:56.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:56.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:56.031: INFO:
Jan 16 16:02:58.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:58.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:58.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:02:58.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Jan 16 16:02:58.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:02:58.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:02:58.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:02:58.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:58.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:02:58.031: INFO:
Jan 16 16:03:00.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:00.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:00.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:00.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Jan 16 16:03:00.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:00.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:00.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:00.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:00.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:00.030: INFO:
Jan 16 16:03:02.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:02.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:02.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:02.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Jan 16 16:03:02.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:02.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:02.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:02.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:02.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:02.035: INFO:
Jan 16 16:03:04.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:04.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:04.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:04.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Jan 16 16:03:04.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:04.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:04.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:04.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:04.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:04.034: INFO:
Jan 16 16:03:06.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:06.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:06.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:06.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Jan 16 16:03:06.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:06.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:06.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:06.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:06.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:06.040: INFO:
Jan 16 16:03:08.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:08.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:08.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:08.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Jan 16 16:03:08.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:08.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:08.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:08.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:08.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:08.031: INFO:
Jan 16 16:03:10.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:10.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:10.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:10.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Jan 16 16:03:10.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:10.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:10.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:10.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:10.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:10.031: INFO:
Jan 16 16:03:12.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:12.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:12.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:12.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Jan 16 16:03:12.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:12.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:12.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:12.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:12.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:12.031: INFO:
Jan 16 16:03:14.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:14.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:14.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:14.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Jan 16 16:03:14.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:14.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:14.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:14.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:14.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:14.035: INFO:
Jan 16 16:03:16.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:16.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:16.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:16.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Jan 16 16:03:16.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:16.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:16.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:16.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:16.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:16.033: INFO:
Jan 16 16:03:18.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:18.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:18.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:18.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Jan 16 16:03:18.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:18.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:18.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:18.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:18.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:18.032: INFO:
Jan 16 16:03:20.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:20.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:20.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:20.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Jan 16 16:03:20.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:20.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:20.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:20.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:20.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:20.032: INFO:
Jan 16 16:03:22.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:22.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:22.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:22.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Jan 16 16:03:22.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:22.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:22.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:22.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:22.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:22.031: INFO:
Jan 16 16:03:24.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:24.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:24.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:24.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Jan 16 16:03:24.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:24.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:24.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:24.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:24.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:24.033: INFO:
Jan 16 16:03:26.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:26.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:26.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:26.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Jan 16 16:03:26.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:26.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:26.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:26.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:26.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:26.031: INFO:
Jan 16 16:03:28.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:28.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:28.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:28.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Jan 16 16:03:28.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:28.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:28.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:28.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:28.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:28.032: INFO:
Jan 16 16:03:30.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:30.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:30.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:30.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Jan 16 16:03:30.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:30.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:30.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:30.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:30.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:30.033: INFO:
Jan 16 16:03:32.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:32.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:32.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:32.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Jan 16 16:03:32.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:32.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:32.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:32.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:32.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:32.032: INFO:
Jan 16 16:03:34.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:34.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:34.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:34.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Jan 16 16:03:34.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:34.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:34.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:34.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:34.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:34.033: INFO:
Jan 16 16:03:36.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:36.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:36.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:36.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Jan 16 16:03:36.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:36.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:36.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:36.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:36.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:36.035: INFO:
Jan 16 16:03:38.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:38.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:38.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:38.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Jan 16 16:03:38.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:38.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:38.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:38.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:38.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:38.031: INFO:
Jan 16 16:03:40.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:40.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:40.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:40.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Jan 16 16:03:40.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:40.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:40.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:40.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:40.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:40.031: INFO:
Jan 16 16:03:42.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:42.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:42.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:42.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Jan 16 16:03:42.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:42.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:42.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:42.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:42.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:42.034: INFO:
Jan 16 16:03:44.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:44.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:44.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:44.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Jan 16 16:03:44.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:44.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:44.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:44.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:44.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:44.031: INFO:
Jan 16 16:03:46.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:46.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:46.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:46.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Jan 16 16:03:46.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:46.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:46.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:46.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:46.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:46.033: INFO:
Jan 16 16:03:48.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:48.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:48.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:48.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Jan 16 16:03:48.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:48.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:48.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:48.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:48.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:48.029: INFO:
Jan 16 16:03:50.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:50.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:50.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:50.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Jan 16 16:03:50.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:50.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:50.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:50.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:50.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:50.030: INFO:
Jan 16 16:03:52.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:52.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:52.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:52.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Jan 16 16:03:52.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:52.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:52.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:52.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:52.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:52.030: INFO:
Jan 16 16:03:54.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:54.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:54.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:54.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Jan 16 16:03:54.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:54.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:54.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:54.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:54.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:54.029: INFO:
Jan 16 16:03:56.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:56.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:56.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:56.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Jan 16 16:03:56.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:56.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:56.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:56.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:56.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:56.030: INFO:
Jan 16 16:03:58.029: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:58.029: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:58.029: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:03:58.029: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Jan 16 16:03:58.029: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:03:58.029: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:03:58.029: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:03:58.029: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:58.029: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:03:58.029: INFO:
Jan 16 16:04:00.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:00.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:00.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:00.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Jan 16 16:04:00.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:00.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:00.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:00.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:00.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:00.030: INFO:
Jan 16 16:04:02.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:02.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:02.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:02.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Jan 16 16:04:02.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:02.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:02.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:02.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:02.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:02.034: INFO:
Jan 16 16:04:04.054: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:04.054: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:04.054: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:04.054: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Jan 16 16:04:04.054: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:04.054: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:04.054: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:04.054: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:04.054: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:04.054: INFO:
Jan 16 16:04:06.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:06.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:06.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:06.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Jan 16 16:04:06.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:06.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:06.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:06.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:06.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:06.040: INFO:
Jan 16 16:04:08.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:08.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:08.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:08.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Jan 16 16:04:08.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:08.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:08.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:08.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:08.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:08.039: INFO:
Jan 16 16:04:10.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:10.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:10.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:10.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Jan 16 16:04:10.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:10.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:10.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:10.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:10.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:10.039: INFO:
Jan 16 16:04:12.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:12.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:12.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:12.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Jan 16 16:04:12.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:12.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:12.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:12.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:12.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:12.036: INFO:
Jan 16 16:04:14.042: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:14.043: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:14.043: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:14.043: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Jan 16 16:04:14.043: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:14.043: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:14.043: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:14.043: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:14.043: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:14.043: INFO:
Jan 16 16:04:16.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:16.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:16.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:16.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Jan 16 16:04:16.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:16.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:16.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:16.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:16.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:16.035: INFO:
Jan 16 16:04:18.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:18.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:18.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:18.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Jan 16 16:04:18.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:18.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:18.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:18.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:18.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:18.033: INFO:
Jan 16 16:04:20.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:20.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:20.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:20.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Jan 16 16:04:20.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:20.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:20.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:20.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:20.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:20.035: INFO:
Jan 16 16:04:22.242: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:22.242: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:22.242: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:22.242: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Jan 16 16:04:22.242: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:22.242: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:22.242: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:22.242: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:22.242: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:22.242: INFO:
Jan 16 16:04:24.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:24.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:24.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:24.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Jan 16 16:04:24.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:24.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:24.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:24.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:24.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:24.034: INFO:
Jan 16 16:04:26.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:26.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:26.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:26.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Jan 16 16:04:26.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:26.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:26.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:26.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:26.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:26.036: INFO:
Jan 16 16:04:28.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:28.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:28.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:28.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Jan 16 16:04:28.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:28.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:28.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:28.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:28.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:28.039: INFO:
Jan 16 16:04:30.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:30.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:30.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:30.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Jan 16 16:04:30.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:30.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:30.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:30.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:30.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:30.039: INFO:
Jan 16 16:04:32.044: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:32.044: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:32.044: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:32.044: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Jan 16 16:04:32.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:32.044: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:32.044: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:32.044: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:32.044: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:32.044: INFO:
Jan 16 16:04:34.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:34.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:34.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:34.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Jan 16 16:04:34.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:34.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:34.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:34.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:34.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:34.035: INFO:
Jan 16 16:04:36.044: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:36.044: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:36.044: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:36.044: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Jan 16 16:04:36.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:36.044: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:36.044: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:36.044: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:36.044: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:36.044: INFO:
Jan 16 16:04:38.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:38.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:38.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:38.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Jan 16 16:04:38.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:38.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:38.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:38.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:38.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:38.038: INFO:
Jan 16 16:04:40.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:40.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:40.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:40.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Jan 16 16:04:40.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:40.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:40.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:40.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:40.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:40.039: INFO:
Jan 16 16:04:42.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:42.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:42.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:42.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Jan 16 16:04:42.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:42.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:42.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:42.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:42.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:42.035: INFO:
Jan 16 16:04:44.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:44.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:44.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:44.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Jan 16 16:04:44.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:44.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:44.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:44.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:44.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:44.034: INFO:
Jan 16 16:04:46.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:46.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:46.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:46.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Jan 16 16:04:46.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:46.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:46.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:46.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:46.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:46.039: INFO:
Jan 16 16:04:48.031: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:48.031: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:48.031: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:48.031: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Jan 16 16:04:48.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:48.031: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:48.031: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:48.031: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:48.031: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:48.031: INFO:
Jan 16 16:04:50.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:50.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:50.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:50.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Jan 16 16:04:50.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:50.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:50.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:50.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:50.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:50.040: INFO:
Jan 16 16:04:52.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:52.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:52.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:52.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Jan 16 16:04:52.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:52.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:52.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:52.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:52.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:52.037: INFO:
Jan 16 16:04:54.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:54.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:54.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:54.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Jan 16 16:04:54.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:54.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:54.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:54.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:54.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:54.034: INFO:
Jan 16 16:04:56.044: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:56.044: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:56.044: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:56.044: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Jan 16 16:04:56.044: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:56.044: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:56.044: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:56.044: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:56.044: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:56.044: INFO:
Jan 16 16:04:58.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:58.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:58.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:04:58.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Jan 16 16:04:58.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:04:58.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:04:58.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:04:58.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:58.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:04:58.038: INFO:
Jan 16 16:05:00.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:00.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:00.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:00.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Jan 16 16:05:00.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:00.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:00.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:00.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:00.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:00.036: INFO:
Jan 16 16:05:02.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:02.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:02.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:02.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Jan 16 16:05:02.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:02.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:02.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:02.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:02.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:02.040: INFO:
Jan 16 16:05:04.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:04.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:04.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:04.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Jan 16 16:05:04.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:04.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:04.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:04.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:04.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:04.040: INFO:
Jan 16 16:05:06.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:06.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:06.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:06.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Jan 16 16:05:06.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:06.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:06.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:06.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:06.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:06.036: INFO:
Jan 16 16:05:08.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:08.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:08.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:08.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Jan 16 16:05:08.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:08.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:08.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:08.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:08.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:08.033: INFO:
Jan 16 16:05:10.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:10.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:10.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:10.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Jan 16 16:05:10.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:10.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:10.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:10.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:10.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:10.036: INFO:
Jan 16 16:05:12.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:12.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:12.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:12.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Jan 16 16:05:12.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:12.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:12.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:12.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:12.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:12.035: INFO:
Jan 16 16:05:14.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:14.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:14.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:14.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Jan 16 16:05:14.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:14.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:14.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:14.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:14.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:14.034: INFO:
Jan 16 16:05:16.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:16.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:16.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:16.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Jan 16 16:05:16.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:16.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:16.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:16.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:16.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:16.034: INFO:
Jan 16 16:05:18.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:18.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:18.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:18.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Jan 16 16:05:18.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:18.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:18.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:18.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:18.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:18.035: INFO:
Jan 16 16:05:20.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:20.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:20.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:20.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Jan 16 16:05:20.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:20.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:20.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:20.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:20.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:20.033: INFO:
Jan 16 16:05:22.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:22.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:22.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:22.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Jan 16 16:05:22.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:22.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:22.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:22.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:22.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:22.036: INFO:
Jan 16 16:05:24.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:24.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:24.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:24.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Jan 16 16:05:24.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:24.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:24.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:24.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:24.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:24.040: INFO:
Jan 16 16:05:26.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:26.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:26.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:26.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Jan 16 16:05:26.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:26.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:26.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:26.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:26.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:26.040: INFO:
Jan 16 16:05:28.045: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:28.045: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:28.045: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:28.045: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Jan 16 16:05:28.045: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:28.045: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:28.045: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:28.045: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:28.045: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:28.045: INFO:
Jan 16 16:05:30.047: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:30.047: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:30.047: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:30.047: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Jan 16 16:05:30.047: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:30.047: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:30.047: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:30.047: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:30.047: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:30.047: INFO:
Jan 16 16:05:32.041: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:32.041: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:32.041: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:32.041: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Jan 16 16:05:32.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:32.041: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:32.041: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:32.041: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:32.041: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:32.041: INFO:
Jan 16 16:05:34.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:34.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:34.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:34.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Jan 16 16:05:34.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:34.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:34.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:34.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:34.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:34.032: INFO:
Jan 16 16:05:36.062: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:36.062: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:36.062: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:36.062: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Jan 16 16:05:36.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:36.062: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:36.062: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:36.062: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:36.062: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:36.062: INFO:
Jan 16 16:05:38.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:38.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:38.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:38.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Jan 16 16:05:38.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:38.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:38.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:38.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:38.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:38.039: INFO:
Jan 16 16:05:40.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:40.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:40.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:40.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Jan 16 16:05:40.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:40.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:40.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:40.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:40.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:40.032: INFO:
Jan 16 16:05:42.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:42.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:42.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:42.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Jan 16 16:05:42.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:42.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:42.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:42.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:42.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:42.036: INFO:
Jan 16 16:05:44.041: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:44.041: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:44.041: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:44.041: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Jan 16 16:05:44.041: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:44.041: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:44.041: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:44.042: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:44.042: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:44.042: INFO:
Jan 16 16:05:46.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:46.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:46.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:46.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Jan 16 16:05:46.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:46.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:46.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:46.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:46.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:46.037: INFO:
Jan 16 16:05:48.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:48.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:48.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:48.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Jan 16 16:05:48.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:48.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:48.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:48.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:48.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:48.035: INFO:
Jan 16 16:05:50.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:50.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:50.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:50.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Jan 16 16:05:50.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:50.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:50.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:50.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:50.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:50.035: INFO:
Jan 16 16:05:52.042: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:52.042: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:52.042: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:52.042: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Jan 16 16:05:52.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:52.042: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:52.042: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:52.042: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:52.042: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:52.042: INFO:
Jan 16 16:05:54.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:54.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:54.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:54.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Jan 16 16:05:54.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:54.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:54.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:54.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:54.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:54.034: INFO:
Jan 16 16:05:56.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:56.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:56.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:56.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Jan 16 16:05:56.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:56.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:56.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:56.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:56.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:56.037: INFO:
Jan 16 16:05:58.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:58.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:58.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:05:58.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Jan 16 16:05:58.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:05:58.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:05:58.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:05:58.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:58.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:05:58.039: INFO:
Jan 16 16:06:00.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:00.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:00.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:00.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Jan 16 16:06:00.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:00.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:00.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:00.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:00.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:00.036: INFO:
Jan 16 16:06:02.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:02.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:02.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:02.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Jan 16 16:06:02.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:02.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:02.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:02.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:02.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:02.038: INFO:
Jan 16 16:06:04.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:04.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:04.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:04.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Jan 16 16:06:04.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:04.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:04.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:04.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:04.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:04.034: INFO:
Jan 16 16:06:06.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:06.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:06.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:06.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Jan 16 16:06:06.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:06.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:06.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:06.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:06.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:06.038: INFO:
Jan 16 16:06:08.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:08.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:08.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:08.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Jan 16 16:06:08.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:08.033: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:08.033: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:08.033: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:08.033: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:08.033: INFO:
Jan 16 16:06:10.063: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:10.063: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:10.063: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:10.063: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Jan 16 16:06:10.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:10.063: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:10.063: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:10.063: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:10.063: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:10.063: INFO:
Jan 16 16:06:12.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:12.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:12.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:12.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Jan 16 16:06:12.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:12.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:12.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:12.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:12.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:12.037: INFO:
Jan 16 16:06:14.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:14.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:14.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:14.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Jan 16 16:06:14.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:14.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:14.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:14.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:14.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:14.035: INFO:
Jan 16 16:06:16.050: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:16.050: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:16.050: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:16.050: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Jan 16 16:06:16.050: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:16.050: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:16.050: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:16.050: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:16.050: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:16.050: INFO:
Jan 16 16:06:18.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:18.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:18.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:18.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Jan 16 16:06:18.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:18.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:18.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:18.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:18.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:18.032: INFO:
Jan 16 16:06:20.042: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:20.042: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:20.042: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:20.042: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Jan 16 16:06:20.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:20.042: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:20.042: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:20.042: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:20.042: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:20.042: INFO:
Jan 16 16:06:22.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:22.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:22.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:22.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Jan 16 16:06:22.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:22.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:22.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:22.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:22.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:22.037: INFO:
Jan 16 16:06:24.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:24.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:24.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:24.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Jan 16 16:06:24.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:24.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:24.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:24.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:24.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:24.036: INFO:
Jan 16 16:06:26.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:26.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:26.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:26.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Jan 16 16:06:26.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:26.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:26.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:26.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:26.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:26.040: INFO:
Jan 16 16:06:28.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:28.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:28.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:28.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Jan 16 16:06:28.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:28.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:28.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:28.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:28.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:28.039: INFO:
Jan 16 16:06:30.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:30.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:30.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:30.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Jan 16 16:06:30.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:30.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:30.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:30.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:30.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:30.035: INFO:
Jan 16 16:06:32.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:32.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:32.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:32.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Jan 16 16:06:32.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:32.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:32.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:32.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:32.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:32.035: INFO:
Jan 16 16:06:34.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:34.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:34.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:34.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Jan 16 16:06:34.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:34.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:34.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:34.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:34.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:34.036: INFO:
Jan 16 16:06:36.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:36.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:36.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:36.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Jan 16 16:06:36.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:36.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:36.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:36.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:36.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:36.036: INFO:
Jan 16 16:06:38.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:38.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:38.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:38.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Jan 16 16:06:38.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:38.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:38.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:38.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:38.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:38.036: INFO:
Jan 16 16:06:40.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:40.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:40.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:40.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Jan 16 16:06:40.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:40.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:40.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:40.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:40.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:40.030: INFO:
Jan 16 16:06:42.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:42.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:42.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:42.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Jan 16 16:06:42.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:42.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:42.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:42.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:42.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:42.032: INFO:
Jan 16 16:06:44.054: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:44.054: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:44.054: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:44.054: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Jan 16 16:06:44.054: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:44.054: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:44.054: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:44.054: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:44.054: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:44.054: INFO:
Jan 16 16:06:46.053: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:46.053: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:46.053: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:46.053: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Jan 16 16:06:46.053: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:46.053: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:46.053: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:46.053: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:46.053: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:46.053: INFO:
Jan 16 16:06:48.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:48.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:48.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:48.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Jan 16 16:06:48.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:48.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:48.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:48.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:48.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:48.034: INFO:
Jan 16 16:06:50.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:50.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:50.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:50.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Jan 16 16:06:50.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:50.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:50.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:50.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:50.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:50.034: INFO:
Jan 16 16:06:52.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:52.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:52.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:52.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Jan 16 16:06:52.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:52.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:52.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:52.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:52.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:52.034: INFO:
Jan 16 16:06:54.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:54.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:54.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:54.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Jan 16 16:06:54.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:54.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:54.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:54.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:54.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:54.036: INFO:
Jan 16 16:06:56.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:56.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:56.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:56.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Jan 16 16:06:56.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:56.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:56.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:56.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:56.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:56.036: INFO:
Jan 16 16:06:58.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:58.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:58.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:06:58.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Jan 16 16:06:58.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:06:58.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:06:58.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:06:58.040: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:58.040: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:06:58.040: INFO:
Jan 16 16:07:00.037: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:00.037: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:00.037: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:00.037: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Jan 16 16:07:00.037: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:00.037: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:00.037: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:00.037: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:00.037: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:00.037: INFO:
Jan 16 16:07:02.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:02.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:02.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:02.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Jan 16 16:07:02.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:02.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:02.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:02.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:02.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:02.035: INFO:
Jan 16 16:07:04.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:04.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:04.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:04.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Jan 16 16:07:04.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:04.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:04.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:04.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:04.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:04.039: INFO:
Jan 16 16:07:06.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:06.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:06.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:06.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Jan 16 16:07:06.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:06.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:06.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:06.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:06.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:06.038: INFO:
Jan 16 16:07:08.030: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:08.030: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:08.030: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:08.030: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Jan 16 16:07:08.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:08.030: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:08.030: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:08.030: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:08.030: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:08.030: INFO:
Jan 16 16:07:10.051: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:10.051: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:10.051: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:10.051: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Jan 16 16:07:10.051: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:10.051: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:10.051: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:10.051: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:10.051: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:10.051: INFO:
Jan 16 16:07:12.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:12.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:12.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:12.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Jan 16 16:07:12.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:12.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:12.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:12.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:12.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:12.038: INFO:
Jan 16 16:07:14.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:14.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:14.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:14.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Jan 16 16:07:14.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:14.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:14.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:14.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:14.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:14.039: INFO:
Jan 16 16:07:16.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:16.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:16.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:16.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Jan 16 16:07:16.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:16.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:16.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:16.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:16.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:16.034: INFO:
Jan 16 16:07:18.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:18.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:18.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:18.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Jan 16 16:07:18.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:18.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:18.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:18.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:18.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:18.034: INFO:
Jan 16 16:07:20.040: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:20.040: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:20.040: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:20.040: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Jan 16 16:07:20.040: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:20.040: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:20.040: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:20.041: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:20.041: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:20.041: INFO:
Jan 16 16:07:22.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:22.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:22.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:22.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Jan 16 16:07:22.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:22.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:22.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:22.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:22.035: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:22.035: INFO:
Jan 16 16:07:24.035: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:24.035: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:24.035: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:24.035: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Jan 16 16:07:24.035: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:24.035: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:24.035: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:24.035: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:24.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:24.036: INFO:
Jan 16 16:07:26.039: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:26.039: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:26.039: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:26.039: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Jan 16 16:07:26.039: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:26.039: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:26.039: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:26.039: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:26.039: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:26.039: INFO:
Jan 16 16:07:28.042: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:28.042: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:28.042: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:28.042: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Jan 16 16:07:28.042: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:28.042: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:28.042: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:28.042: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:28.042: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:28.042: INFO:
Jan 16 16:07:30.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:30.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:30.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:30.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Jan 16 16:07:30.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:30.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:30.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:30.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:30.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:30.036: INFO:
Jan 16 16:07:32.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:32.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:32.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:32.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Jan 16 16:07:32.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:32.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:32.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:32.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:32.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:32.038: INFO:
Jan 16 16:07:34.032: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:34.032: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:34.032: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:34.032: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Jan 16 16:07:34.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:34.032: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:34.032: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:34.032: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:34.032: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:34.032: INFO:
Jan 16 16:07:36.036: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:36.036: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:36.036: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:36.036: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Jan 16 16:07:36.036: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:36.036: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:36.036: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:36.036: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:36.036: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:36.036: INFO:
Jan 16 16:07:38.038: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:38.038: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:38.038: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:38.038: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Jan 16 16:07:38.038: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:38.038: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:38.038: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:38.038: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:38.038: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:38.038: INFO:
Jan 16 16:07:40.034: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:40.034: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:40.034: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:40.034: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Jan 16 16:07:40.034: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:40.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:40.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:40.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:40.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:40.034: INFO:
Jan 16 16:07:42.033: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:42.033: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:42.033: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:42.033: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 16 16:07:42.033: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:42.034: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:42.034: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:42.034: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:42.034: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:42.034: INFO:
Jan 16 16:07:42.169: INFO: The status of Pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:42.169: INFO: The status of Pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:42.169: INFO: The status of Pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan 16 16:07:42.169: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Jan 16 16:07:42.169: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Jan 16 16:07:42.169: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:42.169: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:42.169: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:42.169: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:42.169: INFO:
STEP: Collecting events from namespace "kube-system". - test/e2e/framework/debug/dump.go:42 @ 01/16/23 16:07:42.169
STEP: Found 117 events. - test/e2e/framework/debug/dump.go:46 @ 01/16/23 16:07:42.224
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:33 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-g30srl-control-plane-fncb4_44f5a520-a8cc-477d-b0d4-993b5dd93752 became leader
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:34 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-g30srl-control-plane-fncb4_fe85e234-b780-4510-b032-c503f6de8b01 became leader
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:38 +0000 UTC - event for kube-apiserver-capz-conf-g30srl-control-plane-fncb4: {node-controller } NodeNotReady: Node is not ready
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:38 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-lwdz9
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:38 +0000 UTC - event for kube-proxy-lwdz9: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-lwdz9 to capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:39 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:39 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-2gx65
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:39 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-j8x9j
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:39 +0000 UTC - event for coredns-56f4c55bf9-2gx65: {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 16 16:07:42.224: INFO: At 2023-01-16 15:54:39 +0000 UTC - event for coredns-56f4c55bf9-j8x9j: {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 16 16:07:42.224: INFO: At 2023-01-16 15:54:39 +0000 UTC - event for kube-proxy-lwdz9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:41 +0000 UTC - event for kube-proxy-lwdz9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274" in 1.498501667s (1.498557571s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:41 +0000 UTC - event for kube-proxy-lwdz9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container kube-proxy
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:54:41 +0000 UTC - event for kube-proxy-lwdz9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container kube-proxy
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:12 +0000 UTC - event for coredns-56f4c55bf9-2gx65: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-2gx65 to capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:12 +0000 UTC - event for coredns-56f4c55bf9-2gx65: {kubelet capz-conf-g30srl-control-plane-fncb4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "eca06d256a0ce40287e94de2098d9009592a06289a720ce41d26f4077f73c3e6": 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 16 16:07:42.224: INFO: At 2023-01-16 15:55:12 +0000 UTC - event for coredns-56f4c55bf9-j8x9j: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-j8x9j to capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:12 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:12 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-zrwfv
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:12 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {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 16 16:07:42.224: INFO: At 2023-01-16 15:55:13 +0000 UTC - event for coredns-56f4c55bf9-j8x9j: {kubelet capz-conf-g30srl-control-plane-fncb4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "34710dd753e7b6545603e6cfeff54f5c2eb210a00dca79da166e052050204032": 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 16 16:07:42.224: INFO: At 2023-01-16 15:55:13 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-zrwfv to capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:14 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {kubelet capz-conf-g30srl-control-plane-fncb4} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "bd652032142fc6002c1cc9e3cd123a3fce6f7221cc82f052bfdfc57b4ac49abf": 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 16 16:07:42.224: INFO: At 2023-01-16 15:55:26 +0000 UTC - event for coredns-56f4c55bf9-2gx65: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:26 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:28 +0000 UTC - event for coredns-56f4c55bf9-2gx65: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container coredns
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:28 +0000 UTC - event for coredns-56f4c55bf9-2gx65: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container coredns
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:28 +0000 UTC - event for coredns-56f4c55bf9-j8x9j: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container coredns
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:28 +0000 UTC - event for coredns-56f4c55bf9-j8x9j: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:28 +0000 UTC - event for coredns-56f4c55bf9-j8x9j: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container coredns
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:33 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container metrics-server
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:33 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container metrics-server
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:33 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 6.996405243s (6.996441546s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:34 +0000 UTC - event for metrics-server-c9574f845-zrwfv: {kubelet capz-conf-g30srl-control-plane-fncb4} Unhealthy: Liveness probe failed: Get "https://192.168.161.193:4443/livez": dial tcp 192.168.161.193:4443: connect: connection refused
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:56 +0000 UTC - event for csi-azuredisk-controller: {deployment-controller } ScalingReplicaSet: Scaled up replica set csi-azuredisk-controller-7c87ff77db to 1
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:56 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db: {replicaset-controller } SuccessfulCreate: Created pod: csi-azuredisk-controller-7c87ff77db-x84w9
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:56 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-controller-7c87ff77db-x84w9 to capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:56 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-ggqmt
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:56 +0000 UTC - event for csi-azuredisk-node-ggqmt: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-ggqmt to capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:57 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:57 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:58 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:58 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 946.63712ms (946.755419ms including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:58 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:55:58 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:00 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:00 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0" in 2.252544093s (3.046808121s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:00 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container csi-provisioner
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:00 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container csi-provisioner
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:01 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:01 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container node-driver-registrar
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:01 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container node-driver-registrar
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:01 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 974.128192ms (3.015159471s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:03 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0" in 2.434601199s (3.1942526s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:03 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container csi-attacher
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:03 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:03 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container csi-attacher
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:16 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 12.805675937s (15.063739966s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:16 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:16 +0000 UTC - event for csi-azuredisk-node-ggqmt: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:20 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:20 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container csi-snapshotter
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:20 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" in 3.797537008s (16.406607656s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:20 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container csi-snapshotter
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:22 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0" in 2.39729251s (2.397305711s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:22 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container csi-resizer
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" already present on machine
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Created: Created container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" already present on machine
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container csi-resizer
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-x84w9: {kubelet capz-conf-g30srl-control-plane-fncb4} Started: Started container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:23 +0000 UTC - event for external-attacher-leader-disk-csi-azure-com: {external-attacher-leader-disk.csi.azure.com/capz-conf-g30srl-control-plane-fncb4 } LeaderElection: capz-conf-g30srl-control-plane-fncb4 became leader
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:24 +0000 UTC - event for disk-csi-azure-com: {disk.csi.azure.com/1673884584116-8081-disk.csi.azure.com } LeaderElection: 1673884584116-8081-disk-csi-azure-com became leader
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:24 +0000 UTC - event for external-resizer-disk-csi-azure-com: {external-resizer-disk-csi-azure-com/capz-conf-g30srl-control-plane-fncb4 } LeaderElection: capz-conf-g30srl-control-plane-fncb4 became leader
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:24 +0000 UTC - event for external-snapshotter-leader-disk-csi-azure-com: {external-snapshotter-leader-disk.csi.azure.com/capz-conf-g30srl-control-plane-fncb4 } LeaderElection: capz-conf-g30srl-control-plane-fncb4 became leader
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:38 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-x8x4z
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:38 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-d2bn6
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:39 +0000 UTC - event for csi-azuredisk-node-x8x4z: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-x8x4z to capz-conf-g30srl-md-0-zcjwc
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:39 +0000 UTC - event for kube-proxy-d2bn6: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-d2bn6 to capz-conf-g30srl-md-0-zcjwc
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:40 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-cdspg
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:40 +0000 UTC - event for csi-azuredisk-node-cdspg: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-cdspg to capz-conf-g30srl-md-0-k26sq
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:40 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-ckhqs
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:40 +0000 UTC - event for kube-proxy-ckhqs: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-ckhqs to capz-conf-g30srl-md-0-k26sq
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:49 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:49 +0000 UTC - event for kube-proxy-ckhqs: {kubelet capz-conf-g30srl-md-0-k26sq} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:50 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:50 +0000 UTC - event for kube-proxy-d2bn6: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Started: Started container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Created: Created container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 758.96484ms (2.234513127s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 899.186579ms (899.269079ms including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Created: Created container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Started: Started container liveness-probe
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for kube-proxy-ckhqs: {kubelet capz-conf-g30srl-md-0-k26sq} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274" in 1.485410777s (1.485496342s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for kube-proxy-ckhqs: {kubelet capz-conf-g30srl-md-0-k26sq} Started: Started container kube-proxy
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:51 +0000 UTC - event for kube-proxy-ckhqs: {kubelet capz-conf-g30srl-md-0-k26sq} Created: Created container kube-proxy
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 2.956248961s (4.515031931s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Created: Created container node-driver-registrar
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Started: Started container node-driver-registrar
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for kube-proxy-d2bn6: {kubelet capz-conf-g30srl-md-0-zcjwc} Created: Created container kube-proxy
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for kube-proxy-d2bn6: {kubelet capz-conf-g30srl-md-0-zcjwc} Started: Started container kube-proxy
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:56:56 +0000 UTC - event for kube-proxy-d2bn6: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274" in 3.04158962s (6.05561357s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:00 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1"
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:00 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Started: Started container node-driver-registrar
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:00 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Created: Created container node-driver-registrar
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:00 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 904.211046ms (8.747011408s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:21 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Started: Started container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:21 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Created: Created container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:21 +0000 UTC - event for csi-azuredisk-node-cdspg: {kubelet capz-conf-g30srl-md-0-k26sq} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 19.921589404s (24.959437563s including waiting)
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:28 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Started: Started container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:28 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Created: Created container azuredisk
Jan 16 16:07:42.224: INFO: At 2023-01-16 15:57:28 +0000 UTC - event for csi-azuredisk-node-x8x4z: {kubelet capz-conf-g30srl-md-0-zcjwc} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 22.783675398s (28.00954711s including waiting)
Jan 16 16:07:42.277: INFO: POD NODE PHASE GRACE CONDITIONS
Jan 16 16:07:42.277: INFO: coredns-56f4c55bf9-2gx65 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:12 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:12 +0000 UTC }]
Jan 16 16:07:42.277: INFO: coredns-56f4c55bf9-j8x9j capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:12 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:12 +0000 UTC }]
Jan 16 16:07:42.277: INFO: csi-azuredisk-controller-7c87ff77db-x84w9 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:56 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:56 +0000 UTC }]
Jan 16 16:07:42.277: INFO: csi-azuredisk-node-cdspg capz-conf-g30srl-md-0-k26sq Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:57:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:57:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:40 +0000 UTC }]
Jan 16 16:07:42.277: INFO: csi-azuredisk-node-ggqmt capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:56 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:56 +0000 UTC }]
Jan 16 16:07:42.277: INFO: csi-azuredisk-node-x8x4z capz-conf-g30srl-md-0-zcjwc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:57:28 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:57:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:38 +0000 UTC }]
Jan 16 16:07:42.277: INFO: etcd-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:37 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:43 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:43 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:37 +0000 UTC }]
Jan 16 16:07:42.277: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:06 +0000 UTC }]
Jan 16 16:07:42.277: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:42.277: INFO: kube-proxy-ckhqs capz-conf-g30srl-md-0-k26sq Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:40 +0000 UTC }]
Jan 16 16:07:42.277: INFO: kube-proxy-d2bn6 capz-conf-g30srl-md-0-zcjwc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:56:38 +0000 UTC }]
Jan 16 16:07:42.277: INFO: kube-proxy-lwdz9 capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:54:38 +0000 UTC }]
Jan 16 16:07:42.277: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
Jan 16 16:07:42.277: INFO: metrics-server-c9574f845-zrwfv capz-conf-g30srl-control-plane-fncb4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:13 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:54 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 15:55:13 +0000 UTC }]
Jan 16 16:07:42.277: INFO:
Jan 16 16:07:44.150: INFO:
Logging node info for node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:44.348: INFO: Node Info: &Node{ObjectMeta:{capz-conf-g30srl-control-plane-fncb4 7b078b3a-c556-4a95-ade9-40b0e7fb2e92 3097 0 2023-01-16 15:54:30 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:eastus2-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-g30srl-control-plane-fncb4 kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone:eastus2-1 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:eastus2-1] map[cluster.x-k8s.io/cluster-name:capz-conf-g30srl cluster.x-k8s.io/cluster-namespace:capz-conf-g30srl cluster.x-k8s.io/machine:capz-conf-g30srl-control-plane-fcjfl cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-g30srl-control-plane csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-g30srl-control-plane-fncb4","disk.csi.azure.com":"capz-conf-g30srl-control-plane-fncb4"} 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.161.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 15:54:30 +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-16 15:54:34 +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-16 15:55:04 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2023-01-16 15:55:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {calico-node Update v1 2023-01-16 15:55:22 +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-16 16:06:50 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-g30srl/providers/Microsoft.Compute/virtualMachines/capz-conf-g30srl-control-plane-fncb4,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 15:55:22 +0000 UTC,LastTransitionTime:2023-01-16 15:55:22 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 16:06:50 +0000 UTC,LastTransitionTime:2023-01-16 15:54:06 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 16:06:50 +0000 UTC,LastTransitionTime:2023-01-16 15:54:06 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 16:06:50 +0000 UTC,LastTransitionTime:2023-01-16 15:54:06 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 16:06:50 +0000 UTC,LastTransitionTime:2023-01-16 15:55:12 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-g30srl-control-plane-fncb4,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:8f71e6bc77c34806bf089aa728a41a3b,SystemUUID:76fc5941-c638-1647-b859-935c382909de,BootID:22e4815c-2e68-45b5-bc93-77ca6d0fd154,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1003+8956da8f44f274,KubeProxyVersion:v1.27.0-alpha.0.1003+8956da8f44f274,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner@sha256:3ef7d954946bd1cf9e5e3564a8d1acf8e5852616f7ae96bcbc5ced8c275483ee mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0],SizeBytes:61391360,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-resizer@sha256:9ba6483d2f8aa6051cb3a50e42d638fc17a6e4699a6689f054969024b7c12944 mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0],SizeBytes:58560473,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-attacher@sha256:bc317fea7e7bbaff65130d7ac6ea7c96bc15eb1f086374b8c3359f11988ac024 mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0],SizeBytes:57948644,},ContainerImage{Names:[docker.io/calico/apiserver@sha256:9819c1b569e60eec4dbab82c1b41cee80fe8af282b25ba2c174b2a00ae555af6 docker.io/calico/apiserver:v3.25.0],SizeBytes:35624155,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:f3d314c50fb13960970bee5c2d76f2743553d2663ef2b8e3dcce99a632b60af2 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:35446863,},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:907ee4f4d9eeaedd198ecb39eabce71de1bb7d5c95938423920780155ba3ad17 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:32311072,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:c45af3a9692d87a527451cf544557138fedf86f92b6e39bf2003e2fdb848dce3 docker.io/calico/kube-controllers:v3.25.0],SizeBytes:31271800,},ContainerImage{Names:[docker.io/calico/typha@sha256:f7e0557e03f422c8ba5fcf64ef0fac054ee99935b5d101a0a50b5e9b65f6a5c5 docker.io/calico/typha:v3.25.0],SizeBytes:28533187,},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:[mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter@sha256:a889e925e15f9423f7842f1b769f64cbcf6a20b6956122836fc835cf22d9073f mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1],SizeBytes:22192414,},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-proxy@sha256:9b04f65bb36e6f8c210f143be8a177c6025954115ccd882540ed461b3e38393b gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:21485066,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:4cdd3611bc56027f180c08e42c7c5d11371119325595f8adfc88d8fcd2871542 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274],SizeBytes:21483021,},ContainerImage{Names:[quay.io/tigera/operator@sha256:89eef35e1bbe8c88792ce69c3f3f38fb9838e58602c570524350b5f3ab127582 quay.io/tigera/operator:v1.29.0],SizeBytes:21108896,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:cb5fba6e65765cc93424768170c13c0a8dfe055ed8625b2276df660c562bf2d4 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:17469373,},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:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},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 16 16:07:44.348: INFO:
Logging kubelet events for node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:44.546: INFO:
Logging pods the kubelet thinks is on node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:44.769: INFO: kube-proxy-lwdz9 started at 2023-01-16 15:54:38 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container kube-proxy ready: true, restart count 0
Jan 16 16:07:44.769: INFO: csi-azuredisk-node-ggqmt started at 2023-01-16 15:55:56 +0000 UTC (0+3 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container azuredisk ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container liveness-probe ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container node-driver-registrar ready: true, restart count 0
Jan 16 16:07:44.769: INFO: kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 started at <nil> (0+0 container statuses recorded)
Jan 16 16:07:44.769: INFO: calico-typha-7468f64946-7v227 started at 2023-01-16 15:54:45 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container calico-typha ready: true, restart count 0
Jan 16 16:07:44.769: INFO: coredns-56f4c55bf9-j8x9j started at 2023-01-16 15:55:12 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container coredns ready: true, restart count 0
Jan 16 16:07:44.769: INFO: calico-kube-controllers-6b7b9c649d-hld6k started at 2023-01-16 15:55:12 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container calico-kube-controllers ready: true, restart count 0
Jan 16 16:07:44.769: INFO: csi-node-driver-2q6lr started at 2023-01-16 15:55:12 +0000 UTC (0+2 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container calico-csi ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container csi-node-driver-registrar ready: true, restart count 0
Jan 16 16:07:44.769: INFO: tigera-operator-54b47459dd-r8826 started at 2023-01-16 15:54:39 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container tigera-operator ready: true, restart count 0
Jan 16 16:07:44.769: INFO: kube-scheduler-capz-conf-g30srl-control-plane-fncb4 started at <nil> (0+0 container statuses recorded)
Jan 16 16:07:44.769: INFO: etcd-capz-conf-g30srl-control-plane-fncb4 started at 2023-01-16 15:54:37 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container etcd ready: true, restart count 0
Jan 16 16:07:44.769: INFO: calico-node-gwnfb started at 2023-01-16 15:54:45 +0000 UTC (2+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Init container flexvol-driver ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Init container install-cni ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container calico-node ready: true, restart count 0
Jan 16 16:07:44.769: INFO: coredns-56f4c55bf9-2gx65 started at 2023-01-16 15:55:12 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container coredns ready: true, restart count 0
Jan 16 16:07:44.769: INFO: metrics-server-c9574f845-zrwfv started at 2023-01-16 15:55:13 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container metrics-server ready: true, restart count 0
Jan 16 16:07:44.769: INFO: calico-apiserver-6b65b8d54-5h2m9 started at 2023-01-16 15:55:40 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container calico-apiserver ready: true, restart count 0
Jan 16 16:07:44.769: INFO: csi-azuredisk-controller-7c87ff77db-x84w9 started at 2023-01-16 15:55:56 +0000 UTC (0+6 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container azuredisk ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container csi-attacher ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container csi-provisioner ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container csi-resizer ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container csi-snapshotter ready: true, restart count 0
Jan 16 16:07:44.769: INFO: Container liveness-probe ready: true, restart count 0
Jan 16 16:07:44.769: INFO: kube-apiserver-capz-conf-g30srl-control-plane-fncb4 started at <nil> (0+0 container statuses recorded)
Jan 16 16:07:44.769: INFO: calico-apiserver-6b65b8d54-lttx6 started at 2023-01-16 15:55:40 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:44.769: INFO: Container calico-apiserver ready: true, restart count 0
Jan 16 16:07:45.429: INFO:
Latency metrics for node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:45.429: INFO:
Logging node info for node capz-conf-g30srl-md-0-k26sq
Jan 16 16:07:45.549: INFO: Node Info: &Node{ObjectMeta:{capz-conf-g30srl-md-0-k26sq 988e7a90-6b01-46ca-9e15-e6b0760b3be2 2481 0 2023-01-16 15:56:39 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-g30srl-md-0-k26sq kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-g30srl cluster.x-k8s.io/cluster-namespace:capz-conf-g30srl cluster.x-k8s.io/machine:capz-conf-g30srl-md-0-f557b66f4-bh59m cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-g30srl-md-0-f557b66f4 csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-g30srl-md-0-k26sq","disk.csi.azure.com":"capz-conf-g30srl-md-0-k26sq"} 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.139.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 15:56:39 +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-16 15:56:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-16 15:57:07 +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-16 15:57:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-16 15:57:31 +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-16 16:03:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-g30srl/providers/Microsoft.Compute/virtualMachines/capz-conf-g30srl-md-0-k26sq,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 15:57:31 +0000 UTC,LastTransitionTime:2023-01-16 15:57:31 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 16:03:08 +0000 UTC,LastTransitionTime:2023-01-16 15:56:39 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 16:03:08 +0000 UTC,LastTransitionTime:2023-01-16 15:56:39 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 16:03:08 +0000 UTC,LastTransitionTime:2023-01-16 15:56:39 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 16:03:08 +0000 UTC,LastTransitionTime:2023-01-16 15:57:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-g30srl-md-0-k26sq,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c4a055db6859455fbbd270b541b6e881,SystemUUID:b8230c57-73b5-334f-9c5e-99f6b6940275,BootID:d3d7d5de-ba74-4d1e-8ac1-cad40420f2ff,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1003+8956da8f44f274,KubeProxyVersion:v1.27.0-alpha.0.1003+8956da8f44f274,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:4cdd3611bc56027f180c08e42c7c5d11371119325595f8adfc88d8fcd2871542 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274],SizeBytes:21483021,},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:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},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 16 16:07:45.549: INFO:
Logging kubelet events for node capz-conf-g30srl-md-0-k26sq
Jan 16 16:07:45.747: INFO:
Logging pods the kubelet thinks is on node capz-conf-g30srl-md-0-k26sq
Jan 16 16:07:45.958: INFO: csi-azuredisk-node-cdspg started at 2023-01-16 15:56:46 +0000 UTC (0+3 container statuses recorded)
Jan 16 16:07:45.958: INFO: Container azuredisk ready: true, restart count 0
Jan 16 16:07:45.958: INFO: Container liveness-probe ready: true, restart count 0
Jan 16 16:07:45.958: INFO: Container node-driver-registrar ready: true, restart count 0
Jan 16 16:07:45.958: INFO: kube-proxy-ckhqs started at 2023-01-16 15:56:46 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:45.958: INFO: Container kube-proxy ready: true, restart count 0
Jan 16 16:07:45.958: INFO: calico-node-zr5mg started at 2023-01-16 15:56:46 +0000 UTC (2+1 container statuses recorded)
Jan 16 16:07:45.958: INFO: Init container flexvol-driver ready: true, restart count 0
Jan 16 16:07:45.958: INFO: Init container install-cni ready: true, restart count 0
Jan 16 16:07:45.958: INFO: Container calico-node ready: true, restart count 0
Jan 16 16:07:45.958: INFO: csi-node-driver-xj5bk started at 2023-01-16 15:57:10 +0000 UTC (0+2 container statuses recorded)
Jan 16 16:07:45.958: INFO: Container calico-csi ready: true, restart count 0
Jan 16 16:07:45.958: INFO: Container csi-node-driver-registrar ready: true, restart count 0
Jan 16 16:07:46.583: INFO:
Latency metrics for node capz-conf-g30srl-md-0-k26sq
Jan 16 16:07:46.583: INFO:
Logging node info for node capz-conf-g30srl-md-0-zcjwc
Jan 16 16:07:46.747: INFO: Node Info: &Node{ObjectMeta:{capz-conf-g30srl-md-0-zcjwc f347bd5c-3b6a-49a8-8526-485cffc73aef 2475 0 2023-01-16 15:56:38 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-g30srl-md-0-zcjwc kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-g30srl cluster.x-k8s.io/cluster-namespace:capz-conf-g30srl cluster.x-k8s.io/machine:capz-conf-g30srl-md-0-f557b66f4-mt6wz cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-g30srl-md-0-f557b66f4 csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-g30srl-md-0-zcjwc","disk.csi.azure.com":"capz-conf-g30srl-md-0-zcjwc"} 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.106.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-16 15:56:38 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-16 15:56:38 +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-16 15:56:49 +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-16 15:57:20 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-16 15:57:38 +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-16 16:03:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-g30srl/providers/Microsoft.Compute/virtualMachines/capz-conf-g30srl-md-0-zcjwc,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123176960 0} {<nil>} 4026540Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018319360 0} {<nil>} 3924140Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 15:57:38 +0000 UTC,LastTransitionTime:2023-01-16 15:57:38 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 16:03:06 +0000 UTC,LastTransitionTime:2023-01-16 15:56:38 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 16:03:06 +0000 UTC,LastTransitionTime:2023-01-16 15:56:38 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 16:03:06 +0000 UTC,LastTransitionTime:2023-01-16 15:56:38 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 16:03:06 +0000 UTC,LastTransitionTime:2023-01-16 15:57:20 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-g30srl-md-0-zcjwc,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:55ae4c9787e84e11a3c5d2536b212bb0,SystemUUID:f84cc57d-576a-e349-aa29-d0d822cc5bb2,BootID:d95cde18-998c-4007-926e-491ab96189d1,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1003+8956da8f44f274,KubeProxyVersion:v1.27.0-alpha.0.1003+8956da8f44f274,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},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:[docker.io/calico/typha@sha256:f7e0557e03f422c8ba5fcf64ef0fac054ee99935b5d101a0a50b5e9b65f6a5c5 docker.io/calico/typha:v3.25.0],SizeBytes:28533187,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:4cdd3611bc56027f180c08e42c7c5d11371119325595f8adfc88d8fcd2871542 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_8956da8f44f274],SizeBytes:21483021,},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:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},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 16 16:07:46.748: INFO:
Logging kubelet events for node capz-conf-g30srl-md-0-zcjwc
Jan 16 16:07:46.948: INFO:
Logging pods the kubelet thinks is on node capz-conf-g30srl-md-0-zcjwc
Jan 16 16:07:47.176: INFO: csi-azuredisk-node-x8x4z started at 2023-01-16 15:56:46 +0000 UTC (0+3 container statuses recorded)
Jan 16 16:07:47.176: INFO: Container azuredisk ready: true, restart count 0
Jan 16 16:07:47.176: INFO: Container liveness-probe ready: true, restart count 0
Jan 16 16:07:47.176: INFO: Container node-driver-registrar ready: true, restart count 0
Jan 16 16:07:47.176: INFO: kube-proxy-d2bn6 started at 2023-01-16 15:56:46 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:47.176: INFO: Container kube-proxy ready: true, restart count 0
Jan 16 16:07:47.176: INFO: calico-node-xnq4v started at 2023-01-16 15:56:46 +0000 UTC (2+1 container statuses recorded)
Jan 16 16:07:47.176: INFO: Init container flexvol-driver ready: true, restart count 0
Jan 16 16:07:47.176: INFO: Init container install-cni ready: true, restart count 0
Jan 16 16:07:47.176: INFO: Container calico-node ready: true, restart count 0
Jan 16 16:07:47.176: INFO: calico-typha-7468f64946-qshzj started at 2023-01-16 15:56:46 +0000 UTC (0+1 container statuses recorded)
Jan 16 16:07:47.176: INFO: Container calico-typha ready: true, restart count 0
Jan 16 16:07:47.176: INFO: csi-node-driver-m6slt started at 2023-01-16 15:57:20 +0000 UTC (0+2 container statuses recorded)
Jan 16 16:07:47.176: INFO: Container calico-csi ready: true, restart count 0
Jan 16 16:07:47.176: INFO: Container csi-node-driver-registrar ready: true, restart count 0
Jan 16 16:07:47.796: INFO:
Latency metrics for node capz-conf-g30srl-md-0-zcjwc
Jan 16 16:07:47.970: INFO: Running kubectl logs on non-ready containers in kube-system
Jan 16 16:07:48.347: INFO: Failed to get logs of pod kube-apiserver-capz-conf-g30srl-control-plane-fncb4, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-g30srl-control-plane-fncb4)
Jan 16 16:07:48.347: INFO: Logs of kube-system/kube-apiserver-capz-conf-g30srl-control-plane-fncb4:kube-apiserver on node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:48.347: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-g30srl-control-plane-fncb4:kube-apiserver
Jan 16 16:07:48.747: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-g30srl-control-plane-fncb4, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-g30srl-control-plane-fncb4)
Jan 16 16:07:48.747: INFO: Logs of kube-system/kube-controller-manager-capz-conf-g30srl-control-plane-fncb4:kube-controller-manager on node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:48.747: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-g30srl-control-plane-fncb4:kube-controller-manager
Jan 16 16:07:49.147: INFO: Failed to get logs of pod kube-scheduler-capz-conf-g30srl-control-plane-fncb4, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-g30srl-control-plane-fncb4)
Jan 16 16:07:49.147: INFO: Logs of kube-system/kube-scheduler-capz-conf-g30srl-control-plane-fncb4:kube-scheduler on node capz-conf-g30srl-control-plane-fncb4
Jan 16 16:07:49.147: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-g30srl-control-plane-fncb4: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-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Running [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:06 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:38 +0000 UTC Reason: Message:} {Type:ContainersReady Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:33 +0000 UTC Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 15:54:06 +0000 UTC Reason: Message:}]
kube-controller-manager-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
kube-scheduler-capz-conf-g30srl-control-plane-fncb4 capz-conf-g30srl-control-plane-fncb4 Pending []
In [SynchronizedBeforeSuite] at: test/e2e/e2e.go:251 @ 01/16/23 16:07:49.147
< Exit [SynchronizedBeforeSuite] TOP-LEVEL - test/e2e/e2e.go:77 @ 01/16/23 16:07:49.147 (10m37.701s)
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/16/23 16:07:49.243from 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/16/23 16:07:49.243
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/16/23 16:07:49.244from 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/16/23 16:07:49.244
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/16/23 16:07:49.243from 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/16/23 16:07:49.243
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/16/23 16:07:49.245from 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/16/23 16:07:49.245
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/16/23 16:07:49.246from 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/16/23 16:07:49.246
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/16/23 16:07:49.247from 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/16/23 16:07:49.247
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/16/23 16:07:49.244from 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/16/23 16:07:49.244
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/16/23 16:07:49.246from 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/16/23 16:07:49.246
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/16/23 16:07:49.247from 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/16/23 16:07:49.247
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/16/23 16:07:49.244from 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/16/23 16:07:49.244
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/16/23 16:07:49.245from 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/16/23 16:07:49.245
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e [It] Conformance Tests conformance-tests
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [It] 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 [It] 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 [It] 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 [It] Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e [It] Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e [It] 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 [It] Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e [It] 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 [It] 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 [It] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e [It] 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 [It] 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 [It] Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool
capz-e2e [It] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e [It] Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e [It] Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e [It] Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e [It] 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 [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with out-of-tree cloud provider
capz-e2e [It] [K8s-Upgrade] Running the CSI migration 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 [It] [K8s-Upgrade] Running the CSI migration 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