Domesticating Kubernetes
blog.quickbird.uk
Domesticating Kubernetes
1–10 of 100 posts
Re: Domesticating Kubernetes
#2Only reason I can see RPIs in kubernetes is if you're exclusively using ARM everywhere and/or are running some distributed cluster among different locations (like Chick-fil-a).
Re: Domesticating Kubernetes
#3https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/
here's a live walkthrough - https://www.youtube.com/watch?v=DjpVtNjiXSU
Re: Domesticating Kubernetes
#4Re: Domesticating Kubernetes
#5I can attest to RPI i/o speed: its horrible. Combined with the fact that I have to build Docker containers on the RPIs themselves(because of arm), its more of a hassle than a cool add-on (to be clear I'm running Docker Swarm in a way that isn't too different from the setup of OP). Only reason I can see RPIs in kubernetes is if you're exclusively using ARM everywhere and/or are running some distributed cluster among d…
I recently did this at work, using a single Dockerfile to built multi-arch images for ARM and x64 - it's pretty nice!
Re: Domesticating Kubernetes
#6I can attest to RPI i/o speed: its horrible. Combined with the fact that I have to build Docker containers on the RPIs themselves(because of arm), its more of a hassle than a cool add-on (to be clear I'm running Docker Swarm in a way that isn't too different from the setup of OP). Only reason I can see RPIs in kubernetes is if you're exclusively using ARM everywhere and/or are running some distributed cluster among d…
Re: Domesticating Kubernetes
#7If it's experience deploying applications into containerized environments, then micro-k8s and k3s seem like reasonable choices, you don't really care about the setup of the underlying components, just that they present the k8s API.
If you're looking for experience of managing k8s clusters, then either the distribution you're looking to run in prod. or something like kubeadm are perhaps a better option. kubeadm is very "vanilla" in terms of how it's deployed so it's quite representative of production (on-prem) deployments, perhaps unlike k3s which makes changes to how k8s works.
If you're looking to quickly test things in k8s, I'd recommend kind as the easiest way to stand up and remove clusters quickly.
And if you're looking for something to run your home services long term, I would recommend not using Kubernetes :) (unless you have a really complex home network which might justify adding k8s to the mix)
Re: Domesticating Kubernetes
#8What I miss from all of these tutorials is one very important piece - how to handle network routing and dns automation within your home network, that's in typical scenario is being handled by the ingress/cloud controller. Without having automated (or easy enough) way of reaching the apps you're deploying there, each of these clusters is pretty much useless for users except for maybe learning basics of k8s, what's eas…
Re: Domesticating Kubernetes
#9I can attest to RPI i/o speed: its horrible. Combined with the fact that I have to build Docker containers on the RPIs themselves(because of arm), its more of a hassle than a cool add-on (to be clear I'm running Docker Swarm in a way that isn't too different from the setup of OP). Only reason I can see RPIs in kubernetes is if you're exclusively using ARM everywhere and/or are running some distributed cluster among d…
Re: Domesticating Kubernetes
#10https://www.bretfisher.com/10-minutes-to-highly-available-do...
No good reasons to use K8s outside multi-team enterprise stateful multi-tier architectures.