We have configured our Kubernetes cluster for high availability with two active-active master nodes. However, contrary to our expectations, when one of the master nodes goes down, our cluster becomes non-operational instead of the remaining master node taking over. Specifically, when Master 1 goes down, Master 2 does not take over; and similarly, when Master 2 goes down, Master 1 does not take over. We need to identify and resolve the cause of this issue.
We have configured our Kubernetes cluster for high availability with two active-active master nodes. However, contrary to our expectations, when one of the master nodes goes down, our cluster becomes non-operational instead of the remaining master node taking over. Specifically, when Master 1 goes down, Master 2 does not take over; and similarly, when Master 2 goes down, Master 1 does not take over. We need to identify and resolve the cause of this issue.