Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster

Re:Kubermesh: self-hosted/healing/provisioning, partial-mesh... by mbryant on Sunday August 20, 2017 @05:22PM (#15060316)

There's a better explanation of what's going on over here: http://ocadotechnology.com/blog/creating-a-distributed-data-...

There's some libvirt stuff, but that's mostly for local testing without having a bunch of physical hardware.

The key things I'm trying to do are: - Automatically provision new machines, just by plugging them in. - Don't have a traditional network (i.e. switches)

[ Parent | on HN ]

Re:Kubermesh: self-hosted/healing/provisioning, partial-mesh... by corndoge on Sunday August 20, 2017 @05:41PM (#15060384)

From the article, you're using Quagga -- are you aware of the active fork FRRouting[0]? It was forked about 8 months ago and is over 3,000 commits ahead since most of the core developers have stopped developing Quagga.

[0] https://github.com/FRRouting/frr

[ Parent | on HN ]

Re:Kubermesh: self-hosted/healing/provisioning, partial-mesh... by mbryant on Sunday August 20, 2017 @05:56PM (#15060442)

Yes, but thanks :)

FRRouting took off after I'd already moved on to other things. I've dropped an issue in the repo so I remember, when I get a chance to work on Kubermesh again

[ Parent | on HN ]