-
Notifications
You must be signed in to change notification settings - Fork 14
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
Kubernetes HA - investigate HA Proxy #535
Comments
on branch k3s-ha folder The distributed database is ensure by DQlite. There is a bug if you try to kill master1 dqlite does'nt seems to be able to elect a new leader check this. other than that it works fine. HAProxy configuration can be found here Keepalived configuration can be found here @LeeSmet Can you base on these adapt the tfclient to be able to deploy master nodes with a HA setup ? Like an option to deploy by default 3 master nodes with HA Proxy and keepalived configured and start at launch and with k3s launched with the correct setting (see dcoker-compose file) so that I can test and adapt my kubernetes/startup script and doc ? |
we have to first start master 1 with HAProxy listening on 8443 and keep alive assigning it a virtual IP. |
Closing because we don't have any current plans for this in grid 3.0 |
Investigate HA proxy to see if it fits for our HA deployment of kubernetes
linked to https://github.com/threefoldtech/home/issues/547
The text was updated successfully, but these errors were encountered: