[Sharapolas]

Indeed, as you noticed the networking setup is primitive, but for the time being it works for us. Currently, the hub is chosen to be as reliable as possible and nodes at the end of the spokes are prepared for hub down (ie. they stop safely ).

Kubernetes is more than just Docker containers. Having managed small computing clusters for a decade using custom scripts I find that the value of K8s is how easy it is to manage highly complex applications over an array of loosely connected computing nodes. So in my view k8s includes networking, orchestration and principles of how everything should be done and managed to achieve redundancy, performance and stability.

Containers are just a convenience for simple deployment on asymmetric nodes and is only part of K8s.

[sneak]

If you're actually running kubernetes and you say you're running stuff "in the spirit of kubernetes" it gives the strong impression you are not actually running kubernetes.

I also didn't say your networking was primitive, just that "hub and spoke" and "mesh" are two entirely different things that you seemed to have conflated entirely.

[Sharapolas]

And that is correct. We are indeed not running kubernetes because it is not supported on our hardware and some assumptions were limiting. So we have a new system, but having kubernetes as our ideal.

Hub and spoke is the underlying architecture of the net, but we are achieving mesh like functionality having hub as our central router. The wording might be a bit confusing.