I've been laughing myself of for some minutes, not because the project is uninteresting (I'll be testing it next week on ARM, probably), but because I've decided to call this "Kubernetres" (Being 'TRES' three in Spanish)
why isn’t it called k7?
K3s – Lightweight Kubernetes
61–70 of 194 posts
Re: K3s – Lightweight Kubernetes
#62Welcome 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.
> Welcome to 2019 where an "embedded" system has 1GB RAM. Thirty years ago someone could have said the same when seeing laptop computers and remembering when computer literally used to occupy whole large rooms. Come on, let's stop doing this kind of jokes, they add nothing to the discussion.
Using MicroEJ, RTOS, Zephyr, mbed and other OSes to target Cortex-M4/ESP32 devices already allows for lots of possiblities with 512KB.
Yes 1GB is huge, my Windows Phones are capable of so much with a tiny portion of it.
Re: K3s – Lightweight Kubernetes
#63Not trying to be snarky, just a sincere question - why would you use kubernetes for something like IoT?
I attended KubeCon China last year and there was a very good example of a K8s setup for IoT that scales pretty well. Check these links if you’re curious: - https://schd.ws/hosted_files/kccncchina2018english/18/ShengL... - https://thenewstack.io/rancher-takes-kubernetes-management-t... Disclaimer: not affiliated with any of the companies above. Edit: formatting.
[deleted]
Re: K3s – Lightweight Kubernetes
#64This looks great, we're planning to test with the intention of moving our CI/CD orchestration onto this.
We use Calico internally, is there a plan in the future to allow other SDNs?
Re: K3s – Lightweight Kubernetes
#65Looks quite interesting for small setups, curious to read more about the limitations (E.g. " Added sqlite3 as the default storage mechanism. etcd3 is still available, but not the default. " - what availability promises can this make?)
In terms of etcd3 vs sqlite3, it is as reliable as most airplane systems that depend on it. https://www.sqlite.org/famous.html I think the "high availability by redundancy" story is oversold.
pretty sure critical airline systems have redundancy
Re: K3s – Lightweight Kubernetes
#66Do you think kubernetes are necessary for small businesses?
Necessary, no. But with the hardware almost free, a 3 x Raspberry Pi cluster, switch, access pointer, and a small UPS would be a few $100 which allows for some interesting possibilities. Pretty much any business will want inventory tracking, tracking staff hours, monitoring cameras, sensors for detecting flooding/doors left open/freezers dying, running point of sales terminals, keeping the supply chain running smooth…
Hardware was never the bottleneck there. The systems could cost a hundred times that and it would still be a rounding error on the capex of even the smallest "real" business.
The obstacle to using custom hardware and software in local biz is and has always been, the fact that by relying on it, the one guy who knows how to administer it all becomes the single point of failure for the whole business.
No amount of tooling can save them from that. So local biz will always be beholden to the Oracles of the world, because smart individuals just can't be relied on.
Businesses need to rely on other businesses. A business with a customer service departments and spare stock on hand. K3s or k8s might be used in the technology product offered by such a business, but this by itself won't change the economics of that market.
Re: K3s – Lightweight Kubernetes
#67Earlier quoted context omitted.
> Welcome to 2019 where an "embedded" system has 1GB RAM. Thirty years ago someone could have said the same when seeing laptop computers and remembering when computer literally used to occupy whole large rooms. Come on, let's stop doing this kind of jokes, they add nothing to the discussion.
We're still in a place where there are millions of embedded devices out there in actual real world use where these resource constraints are real.
Would you put or even need Kubernetes for those devices?
Re: K3s – Lightweight Kubernetes
#68Earlier quoted context omitted.
> Welcome to 2019 where an "embedded" system has 1GB RAM. Thirty years ago someone could have said the same when seeing laptop computers and remembering when computer literally used to occupy whole large rooms. Come on, let's stop doing this kind of jokes, they add nothing to the discussion.
At some point in time, the physical realities of electrons and metal wires will kick in. Then the growth will stop and you'll start kicking your own ass about performance and pointer arithmetic and cache policy. Maybe that point in time is now, maybe it isn't. But it is coming nonetheless, that is one thing we can be sure of.
True, but not for all developers.
For at least 50% of developers, the "physical reality" is that of gathering client requirements quickly and accurately and implementing them correctly and on budget.
Not of micro-optimizing CPU cache hits :)
Re: K3s – Lightweight Kubernetes
#69Earlier quoted context omitted.
> Welcome to 2019 where an "embedded" system has 1GB RAM. Thirty years ago someone could have said the same when seeing laptop computers and remembering when computer literally used to occupy whole large rooms. Come on, let's stop doing this kind of jokes, they add nothing to the discussion.
The problem is that the bottom end of 1k RAM still exists. In fact, because the main change is that it gets cheaper every year, it's even more prevalent. Just because there aren't lots of blog posts, doesn't mean that isn't a large proportion of the industry. The word 'embedded' is not well defined, but if you use it on things with 1GB of RAM, what do you call a PIC with 1K? My personal definition of embedded (which…
1K ram embedded device surely doesn't even exist in compute scenarios where kubernetes operates. There's very different fields
Re: K3s – Lightweight Kubernetes
#70This is very nicely done. It annoys me a bit to have to set up a registry and have a build cycle prior to actually deploying things, but gitkube might help there...