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

Kubernetes HA - investigate HA Proxy #535

Closed
zgorizzo69 opened this issue Feb 17, 2020 · 3 comments
Closed

Kubernetes HA - investigate HA Proxy #535

zgorizzo69 opened this issue Feb 17, 2020 · 3 comments
Labels
type_feature New feature or request

Comments

@zgorizzo69
Copy link
Contributor

Investigate HA proxy to see if it fits for our HA deployment of kubernetes

  • Describe setup
  • Document inner working
  • POC

linked to https://github.com/threefoldtech/home/issues/547

@zgorizzo69 zgorizzo69 self-assigned this Feb 17, 2020
@zaibon zaibon added this to the 0.3.0 milestone Feb 19, 2020
@zgorizzo69
Copy link
Contributor Author

on branch k3s-ha folder /docs/kubernetes/ressources/ha/docker
There is a makefile to try the HA setup with HAProxy and keepalive for the FIX registration IP around masters.

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 /docs/kubernetes/ressources/ha/docker/scripts/haproxy.sh

Keepalived configuration can be found here /docs/kubernetes/ressources/ha/docker/scripts/keepalived.sh

@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 ?

@zgorizzo69
Copy link
Contributor Author

we have to first start master 1 with HAProxy listening on 8443 and keep alive assigning it a virtual IP.
Only then we should start the master 2 and 3 with the parameter --server https://{VIRTUAL_IP}:8443
Otherwise there will be no LB if we bind then all to master1 IP

@zaibon zaibon modified the milestones: next, later Jun 26, 2020
@DylanVerstraete
Copy link
Contributor

Closing because we don't have any current plans for this in grid 3.0

@xmonader xmonader added the type_feature New feature or request label Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type_feature New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants