2 hours agoCreated a post • 86 points @punnerud • 10 comments
I thought Kubernetes is not great for environments with poor network connectivity, which is quite common when dealing with Edge and IoT scenarios. Has that changed?Reply
Another vote for K3s. Easy to set up on a Pi cluster.
Pity Istio doesn’t offer an ARM buildReply
Having a RaspberryPi laying idle in a drawer somewhere, I wonder if others have installed microk8s or k3s on it.
What kind of workloads are you running on it? Whoever has OpenFaas installed on your rpi, what type of functions are you running?Reply
Looking forward to this being decoupled from snapd eventually. Until then, not the fientist hope I'd touch this when any alternative exists where snapd can be avoidedReply
Plain k8s has a fearsome reputation as being complex to deploy, which I don't think is quite deserved. It isn't totally straightforward, but the documentation does tend to make it sound a bit worse than it actually is.
I run a couple of small clusters and my Ansible script for installing them is pretty much:
Running in a multi-master setup requires an extra argument to kubeadm init. There are a couple of other bits of faffing about to get metrics working, but the documentation covers that pretty clearly.
* Set up the base system. Set up firewall. Add k8s repo. Keep back kubelet & kubeadm. * Install and configure docker. * On one node, run kubeadm init. Capture the output. * Install flannel networking. * On the other nodes, run the join command that is printed out by kubeadm init.
I'm definitely not knocking k3s/microk8s, they're a great and quick way to experiment with Kubernetes (and so is GKE).Reply
From all of the low-ops K8s distributions, k3s is the best from perspective of inital setup, maintenance and usage on less powerful hardware.
There are even now higher-level tools such as k3os and k3sup to further reduce the initial deployment pains.
MicroK8s prides with 'No APIs added or removed'. That's not that positive in my book. K3s on the other hand actively removes the alpha APIs to reduce the binary size and memory usage. Works great if you only use stable Kubernetes primitives.
Deploying k8s has gotten a lot easier these days -- some alternatives in this space:
k0s is my personal favorite and what I run, the decisions they have made align very well with how I want to run my clusters versus k3s which is similar but slightly different. Of course you also can't go wrong with kubeadm -- it was good enough to use minimally (as in you could imagine sprinkling a tiny bit of ansible and maintaining a cluster easily) years ago, and has only gotten better.Reply
How is persistent storage handled on microk8s (or k3s)?Reply
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.Reply
Now with Windows installer. This could make life a lot easier in many dev environments.Reply
How does it compare against minikube? Seems to be based on Snaps vs minikube's VM-based approach. Any other major pros/cons?Reply