Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The server's High Availability failure #15

Open
SoyluAlaattin opened this issue Mar 27, 2024 · 1 comment
Open

The server's High Availability failure #15

SoyluAlaattin opened this issue Mar 27, 2024 · 1 comment
Assignees

Comments

@SoyluAlaattin
Copy link
Member

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.

@husamettinarabaci
Copy link
Member

Please use a short title and a good large description

@SoyluAlaattin SoyluAlaattin changed the title Master nodes configured with KubeSphere on the server are not working in active-active mode. The server's High Availability failure Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants