If it is as easy to deploy, as they say, it is bound to become the most used implementation as Ubuntu became the most popular Linux distro for servers.
I am looking forward to this.
K3s – Lightweight Kubernetes
141–150 of 194 posts
Re: K3s – Lightweight Kubernetes
#142I find it humorous how many people in this thread seem so willing to use this in production.
If you can't make Vanilla upstream Kubernetes work, it is very ill advised to think you will be met with success using a heavily modified fork that has a fraction of the support of K8S.
Re: K3s – Lightweight Kubernetes
#143Earlier quoted context omitted.
Got excited about this too, but unfortunately no, it doesn't run on Crostini. Fails with querying netfilter. Also tried through docker-compose from the GH repository. It starts the k3s server fine but fails on starting the nodes as they require privileged container mode, which doesn't work on Crostini at the moment.
Mentioned this elsewhere, but if you create an issue, Darren mentioned on the CNCF webinar that they would be looking into ChromeOS soon.
There's also a feature request in ChromeOS bugtracker about adding the missing bits for minikube, part of which seem to be similar to what k3s is using:
https://bugs.chromium.org/p/chromium/issues/detail?id=878034
Re: K3s – Lightweight Kubernetes
#144I'm going to try this - I really hope its good. I've spent a lot of days trying to get k8s working with a cheap home server. With VMs and docker conflicting networks its a nightmare. Upgrading is worse.
I've tuned a Kubernetes setup to run pretty well on a Pi cluster with 1 GB RAM per node here: http://www.pidramble.com — there's a configuration for testing in Vagrant/VirtualBox machines as well.
Hey that looks pretty cool. I bought an old Xeon workstation for $200 off ebay that I think is more flexible. My own rack of blades does sound awesome. :)
Re: K3s – Lightweight Kubernetes
#145Re: K3s – Lightweight Kubernetes
#146Looks 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.
The reliability of sqlite3 is not in question, the reliability of the system running it is. When running in any of the cloud providers you will get systems that briefly lose network connection or just go away. Sometimes with notification, sometimes without. You will have down time if you don't plan for HA. So the question is whether it is worth the complexity trade off for that period of downtime or how many 9s do you need in your SLA.
Re: K3s – Lightweight Kubernetes
#147Earlier 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…
>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?
_very_ embedded
Re: K3s – Lightweight Kubernetes
#148Earlier quoted context omitted.
You missed the point. A day will come when CPU speeds and RAM sizes will stop increasing. When that day comes you don't be able to ignore performance, because a lack of performance will mean actual, real-world dollar costs for the client, and so performance will be the #1 requirement of the client.
I didn't miss it. For the vast majority of applications, which are Line Of Business (LOB) applications, performance doesn't really matter. It's good enough. LOB applications are made to replace humans and they need to be a multiple of times faster than human operations (+ the extra benefits of automation). And the vast majority of them are. And most programmers are working on those applications. So there's 0 incentiv…
Implying nobody would bat an eyelid at performance problems in LOB applications...
Re: K3s – Lightweight Kubernetes
#149I mean, I've built a Kubernetes-y thing for my own needs, mostly "scheduling" LXC and FreeBSD Jails, and it needs hella less than 256MB of RAM and it's around 20MBs. Maybe I should clean the code and publish it.
Re: K3s – Lightweight Kubernetes
#150Earlier quoted context omitted.
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 tooli…
Dunno. I've know several business owners that didn't take credit cards until recently, and even then only did so because the newer companies have significantly lowered the investment cost. Maybe you don't consider small family owned restaurants "real". Seems like there's an opportunity for a cheap 3 node cluster, sold as a value add to businesses and supported a platform that application writers could target. They mi…
"Cluster" doesn't really square with "small business". Like, why have 3 nodes? HA? They're all probably plugged into the same power run and switch and breathing the same A/C. They're not actually redundant but they are more complicated. So it makes no sense unless you have strangely huge/complicated computational requirements.