OKD 4.7.0 cluster crashed and not coming online

[beuteltiger]

Hi,

My cluster crashed and now the api only send empty responses, the masters rebooted and cant start their sdn pods.
The empty responses would indicate that the haproxy doesn't have a backend.

Running pods on the masters are:
CONTAINER CREATED STATE NAME ATTEMPT POD
da7a962a06cdd 4 hours ago Running kube-apiserver
4a8a9e6897675 4 hours ago Running kube-controller-manager
490c3f52240c8 25 hours ago Running etcd-metrics
5f6aaf6ed4dec 25 hours ago Running etcd
650a69bf2f50a 25 hours ago Running etcdctl
ab40d69655021 25 hours ago Running kube-apiserver-check-endpoints
9053773899cf4 25 hours ago Running kube-apiserver-insecure-readyz
0a7e0c0d0b1a7 25 hours ago Running kube-scheduler-recovery-controller
78ec4385b5d8d 25 hours ago Running kube-apiserver-cert-regeneration-controller
3d3f6f60ae759 25 hours ago Running kube-apiserver-cert-syncer
a5551b171c701 25 hours ago Running kube-scheduler-cert-syncer
03724f203c4d1 25 hours ago Running kube-scheduler
775d1aa27a29f 25 hours ago Running kube-controller-manager-recovery-controller
b4382ffe0cec8 25 hours ago Running kube-controller-manager-cert-syncer
548b219514eb7 25 hours ago Running cluster-policy-controller

A pointer into the right direction would be appreciated