31–40 of 194 posts
Earlier quoted context omitted.
Because I want my doors, windows, garage door, smoke alarms, security system, and any other smart thing in my house even when the IoT controller dies. I also want as much functionality as possible if my ISP (Comcast) decides on another "maintenance" window. So that basically means local smarts and fall over in the case of a hardware failure.
Same. What does it have to do with kubernetes?
Earlier quoted context omitted.
What is currently a good alternative for a small business who needs to distribute containers on a handful of nodes? Docker swarm mode?
A single baremetal server with just docker containers. It's much easier to migrate from just containers running on nodes to an orchestration system (marathon, nomad OR k3s/k8s; there are other options) than to start with the orchestration system.
Earlier quoted context omitted.
Like every process, the text segment is demand paged so it doesn't consume ram unless it's actually needed. What you probably mean is that multiple copies of the same library cannot share the same physical memory pages.
Nope, they mean there's no flash memory available on the resource constrained device to store megabytes of useless runtime. Routers/other IOT Linux devices regularly use SPI ROM chips sized 4MB..16MB, you can't just install a 100MB Ubuntu/Arm rootfs on those.
A a few hundreds of megabytes of flash will soon cost less than the plastic and manufacturing costs of the chip itself. At that point, manufacturers will be putting in 128megabyte flash chips simply because 16 megabyte flash chips cost more.
The only place that argument won't apply is in microcontrollers where the flash is on the same die as the CPU.
Welcome to 2019 where an "embedded" system has 1GB RAM. The problem of GO is that all those unused libraries are loaded in RAM instead of staying on disk, and loaded when needed. An helloworld in GO (around 1.6MB) is still too large for my openwrt router.
And it has to run on every node even if the worker nodes are just running workloads.
Do you think kubernetes are necessary for small businesses?
- Rolling update? Build it yourself or get it with k8s - Infrastructure as code? Do it somehow yourself with ansible, awx or other setup OR just use k8s - Running different workloads on a bunch of hardware with resource scheduler -> some trickery or x different kind of vms
I like it very much and i hope and guess that the k8s way will take over a lot. And since i'm working with k8s i really wanna have it at home. k3s sounds like a very good way forward.
If you have a good working little setup, you don't need to replace it with k8s.
Earlier quoted context omitted.
What is currently a good alternative for a small business who needs to distribute containers on a handful of nodes? Docker swarm mode?
Kube is fine for this, but don't roll your own, use GKE. Perhaps you'd be better served using more managed services, though?
Earlier quoted context omitted.
Because I want my doors, windows, garage door, smoke alarms, security system, and any other smart thing in my house even when the IoT controller dies. I also want as much functionality as possible if my ISP (Comcast) decides on another "maintenance" window. So that basically means local smarts and fall over in the case of a hardware failure.
Same. What does it have to do with kubernetes?
Earlier quoted context omitted.
What is currently a good alternative for a small business who needs to distribute containers on a handful of nodes? Docker swarm mode?
A single baremetal server with just docker containers. It's much easier to migrate from just containers running on nodes to an orchestration system (marathon, nomad OR k3s/k8s; there are other options) than to start with the orchestration system.
Docker is on my long term list (maybe) but the current system is fast, stable and requires little intervention so docker would have to offer a massive change not a step change to make it worth it.
I always default to things I know until the benefits are clear and it's worked out well so far.
Practically speaking: I worry this will become a parallel but subtlety different implementation of Kubernetes with it's own quirks.