Unobtrusive version: https://microk8s.io/?cp=hide#cookies
MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
101–110 of 138 posts
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#102Is Snap the only way to install this on linux? This is a non-starter for me.
Doesn't look like it.
https://github.com/ubuntu/microk8s/issues/988#issuecomment-6...
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#103Earlier quoted context omitted.
I mostly gave up on containers on Pis due to the overhead (disk space, deployment hassles with private registries, etc.). Built my own mini-Heroku and run all my services/functions there: https://github.com/piku
+1 to piku. I use it on a homelab server (not a Raspberry Pi) and just love how simple it is. It sets up a Python deploy environment for web apps that is exactly how I'd personally hand-configure the same in production (nginx, uwsgi, git). The best part of the project is that the entire thing is 1,000 lines of open source and readable Python code, so there's truly no magic whatsoever.
My blog used to run on it until I turned it into a static site, but the builder “function” now happily lives alongside a Node-RED install and a bunch of other things on a tinier VM.
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#104Earlier quoted context omitted.
What has been changed to improve k8s for applications with poor connectivity between workers on the edge and the control plane in the cloud?
Other than bugs around bad connections causing hangs (the kubelet is less vulnerable to pathological failures in networking causing it to stall), nothing significant. Kube is designed for nodes to have continuous connectivity to the control plane. If connectivity is disrupted and the machine restarts, none of the workloads will be restarted until connectivity is restored. I.e. if you can have up to 10m of network dis…
Your reply provides a lot of context. Thanks!
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#105Is K8S still eating so many CPU cycles while idle? Last year I checked and every physical machine in a K8S cluster was burning CPU at 20-30% - with zero payload, just to keep itself up! Don´t you feel that this is totally inacceptable in a world with well understood climate challenges?
It still sucks unfortunately
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#106Deploying k8s has gotten a lot easier these days -- some alternatives in this space: - https://docs.k0sproject.io ( https://github.com/k0sproject/k0s ) - https://k3s.io ( https://github.com/k3s-io/k3s/ ) 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 k…
Is developing locally with one of these k8s implementations a good option? My current workflow is to develop locally with a combination of bare (non-containerized) servers and Docker containers, but all of my deployment is to a hosted k8s cluster. If developing locally with k8s would likely be a better workflow, are any of these options better than the others for that?
I use Minikube, I run `eval $(minikube docker-env)` and push my images straight into it - after patching imagePullPolicy to "IfNotPresent" for any resources using snapshot images - as K8s defaults to IfNotPresent, unless the image ends with "snapshot", then it defaults to "Always"...
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#107I moved from k3s to microk8s for local development. I gave up on k3s because I needed calico CNI and it was a pain to set up, on microk8s it's just `microk8s enable calico`. I also found k3s a bit too opinionated with the default Traefik ingress and service-lb.
I think they've moved off the Traefik ingress in favor of others out of the box FWIW.
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#108It hadn't occurred to me that there were multiple different kubernetes. I thought it was essentially just a single app, or rather collection of apps. Are these essentially different choices available for people who wish to self host their k8s clusters? Are there any good resources that summarise the different advantages of each choice? What is the same between all the choices, what are the differences?
Tons of choices, k8s is really just a definition of an API and there lots of things you can plug in at various points to implement parts of the API (or even completely extend it). Read the official docs--they'll walk you through the design and capabilities. As far as what's available, well it's a bit like trying to understand "what's the newest programming languge?" You probably want to plug yourself into the k8s community and start looking at subreddits, SIG meeting notes, community news, etc. New things are popping up literally every day.
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#109Earlier quoted context omitted.
They're Kubernetes distributions. So think of Kubernetes like Linux, and kubeadm, OpenShift, k3s like Ubuntu, Red Hat etc.
What would be the equivalent of the kernel (the bit they all share)?
The k8s API: https://kubernetes.io/docs/concepts/overview/kubernetes-api/
Most distributions will use the stock kubelet process (what runs containers on nodes), but you don't have to--there are kubelet compatible processes to run VMs instead of containers, run webassembly code (krustlet), etc.
Everything in k8s can be swapped out and changed, the API spec is the only constant.
Re: MicroK8s – Low-ops, minimal Kubernetes, for cloud, clusters, Edge and IoT
#110(Full disclaimer - I'm an engineer at Talos, but I believe it's pretty relevant here) If folks are interested in this kind of K8s deployment, they might also be interested at what we're doing at Talos ( https://talos.dev ). We have full support for all of these same environments (we have a great community of k8s-at-home folks running with Raspberry Pis) and a bunch of tooling to make bare metal easier with Cluster AP…
A few questions if I may. I administer a few thousand machines which are provisioned using Puppet, and I've had my eye on a more immutable style of administration integrating K8S.
- How does Talos handle first getting on to the network? For example, some environments might require a static IP/gateway for example to first reach the Internet. Others might require DHCP.
- How does Talos handle upgrades? Can it self upgrade once deployed?
- What hardware can Talos run on? Does it work well with virtualisation?
- To what degree can Talos dynamically configure itself? What I mean by this is if that a new disk is attached, can it partition it and start storing things on it?
- How resilient is Talos to things like filesystem corruption?
- What are the minimum hardware requirements?