We were using the weave CNI on our kubernetes cluster. It started failing, so we called weaveworks to try to buy support. They said no, recommending a differe

We were using the weave CNI on our kubernetes cluster. It started failing, so we called weaveworks to try to buy support. They said no, recommending a different CNI which would necessitate a disruptive cluster replacement. Once that was a necessity, all the other CNIs were on the table and we went with cilium, which has been ok with k8s 1.22 on CentOS 7, but which is now having undiagnosed trouble with k8s 1.24 on Red Hat 8. The messy process of figuring that out is underway.