You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, kube-config enable-master sets the master up as a worker as well as master. It would be nice to have the two separated so they can run independently.
Bonus points for implementing setup of a multimaster cluster.
What are everyone's thoughts on this?
The text was updated successfully, but these errors were encountered:
I'm researching a bit in HA, and have gotten etcd cluster in a sane way at least. HA in Kubernetes is a work-in-progress topic, but I'll suggest that you should join sig-high-availability on Slack.
The HA guru is @mikedanese (sorry for pinging you), and I'll excitedly watch and maybe contribute to the high availability work. The problem right now is to find a reliable bare-metal load-balancer setup.
I may consider k8s-master-only.service in future releases. Thanks
Currently, kube-config enable-master sets the master up as a worker as well as master. It would be nice to have the two separated so they can run independently.
Bonus points for implementing setup of a multimaster cluster.
What are everyone's thoughts on this?
The text was updated successfully, but these errors were encountered: