Hacker News new | past | comments | ask | show | jobs | submit login

If anybody seriously believe that Kubernetes is good on Edge and IoT, our industry is in deep trouble. I usually like Canonical, but this is next level bullshit.



Care to explain why? And what industry you're talking about?

Kubernetes has made efforts for nodes to work with poor network connectivity.

The node requirements aren't that big.

A lot of use cases are relatively easy to containerise.

And edge / IoT devices are getting more powerful as well.

They aren't talking about consumer IoT here as well.

It has become a meme that Kubernetes is complicated. But it solves a lot of orchestration problems that would need to be implemented in other ways.


IDK about OP, but when I think IoT, I think small single purpose devices: a ring door bell, a "smart" thermostat or fire alarm, a security camera. There at most a couple of processes running, what is there to orchestrate on an IoT doorbell?

On the backend where you have services being fed, processing, and presenting all that data sure Kubernetes that part up, but that doesn't seem to need a special distro of Kubernetes.


    when I think IoT, I think small single purpose devices: a ring door bell, a "smart" thermostat or fire alarm, a security camera. There at most a couple of processes running, what is there to orchestrate on an IoT doorbell?
Exactly!


Don't worry, as evidenced by recent posts eg [1] k8s has already entered the trough of disillusionment in its hype cycle for some time now, though Stockholm's is particularly strong on this one given its labyrinthic complexity.

[1]: https://news.ycombinator.com/item?id=27903720


The hype cycle is still strong - the king is naked and you are getting downvoted for saying it.


Edge is a very overloaded term that just means a server not in a datacenter imo, it could be a thick edge with 8 esx, hundreds or cores and gigabytes of memory in a shop or it could be a little single node box in a closet at someone’s home or it could be a light switch.

Technically they’re all edge, but nobody thinks K8s can run on the latter, but it might work on the prior two.


Canonical is just one of several players in this area. There's also k3s and k0s, for example.

I suppose it might depend on what you count as "edge", but we're using kubernetes to distribute a complex product to customers onprem. The product has multiple databases, services, transient processes, scheduled jobs, and machine learning. It needs to be able to run on a single machine or a cluster depending on customer requirements. It needs to support whatever Linux variant the customer allows. Using Kubernetes solves a lot of problems for us.


on-prem is not edge IMO. Edge is something small, far away from datacenters, close to customers with limited compute and storage capacity. Did I get this wrong?

For example, SQLite advertise itself as "database on edge".


"Edge" is kind of a relative term. E.g. relative to a public cloud, anything not in that cloud could be considered edge. Or, if a company's systems are in a shared datacenter somewhere, then the systems in their actual offices might be considered "edge".

Just as an example (not saying it's authoritative):

> "Edge computing is often referred to as 'on-premise.'"

   -- https://dzone.com/articles/demystifying-the-edge-vs-cloud-computing
But these days, people even refer to systems hosted on a company's own cloud account as "on-premise", so these terms get increasingly fuzzy over time.

Btw since you mention SQLite, the k3s system uses SQLite instead of the default etcd used by Kubernetes, for the reason you mention. These systems really are intended to support true edge scenarios. K3s is distributed as a single 40 MB binary, and you can run it on non-PC edge hardware.

For anyone who runs a system that involves multiple containers on a single machine, it can be worth looking at systems like k3s as an alternative to e.g. Docker Compose. There's not much downside other than some learning curve, and it gives you a wealth of capabilities that you otherwise tend to end up hacking together with scripts or whatever.


I guess that depends on your definition of "Edge". There are quite few a "hybrid" (cloud plus on-prem) use cases where running K8s on-prem can be a good option. If you check https://azure.microsoft.com/en-us/products/azure-stack/edge/... those devices can easily run a K8s cluster.


Why? In its smallest form k8s is a few go processes handling a proxy and some container scheduling/runtime logic.

Sure if you run an entire control plane on the edge you're adding more complexity... but you don't have to do that, and control planes are complex beasts by their nature.


IoT devices doesn't even have the memory required for running a k8s worker process. They should run a low-cost, very small embedded system. Most of them doesn't even have a Linux kernel.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: