Earlier quoted context omitted.
No pictures of fog machine and spooky graveyard -- 4/10
Updated.
Awesome. 10/10.
K3s – Lightweight Kubernetes
191–196 of 196 posts
Re: K3s – Lightweight Kubernetes
#192Earlier quoted context omitted.
If you're just messing around, just use kind ( https://kind.sigs.k8s.io ) or minikube if you want VMs ( https://minikube.sigs.k8s.io ). Both work on ARM-based platforms. You can also use k3s; it's hella easy to get started with and it works great.
If you go the kind route, be sure to not use Docker for mac and instead opt for podman which is much more resource efficient. Now that I've switched over to podman, my computer doesn't sound like it's about to blast off when I'm running clusters.
Not a fan of docker for Mac for sure. Podman or Rancher Desktop or Colima are the way to go.
Re: K3s – Lightweight Kubernetes
#193K3s' go.mod[0] is insane. [0] https://github.com/k3s-io/k3s/blob/master/go.mod
My only worry is the 10+ domains (involving 4+ major companies) being used for import paths. I know there are solutions but that would be a mess to figure out 10 years from now when half those links are broken or changed subtly.
Re: K3s – Lightweight Kubernetes
#194Earlier quoted context omitted.
Curious, what have you run into that you couldn’t troubleshoot with a privileged pod with host networking?
I had a situation where the etcd cluster got hosed, making it basically impossible (at least with the ways I know) to interact with the k8s API at all. So I didn't have any way to get a privileged pod running.
Ah gotcha. Haven’t had to deal with that yet. Maybe possible to add a static pod via the machine config? But yeah it’s basically throwing out a bunch of linux admin muscle memory.
Re: K3s – Lightweight Kubernetes
#195Earlier quoted context omitted.
That does not impact 99% of ppl.. The licence change impacts only companies like Digger or Spacelift that build their platform abusing TF oss offering.
That's a bad take and you know it. HashiCorp couldn't make money because their enterprise offering was slim on features and overpriced. Rather than compete, they're playing protect-the-castle with some aggressive plays to keep their company afloat. They're bad stewards of open source (always have been) and are now getting their just desserts.
You can say the same about MariaDB, Elasticsearch, CocroachDB etc.
Why is „AWS attacks OSS” bad and „Spacelift attacks OSS” good ?
Its exactly the same case just size of companies is different.
Re: K3s – Lightweight Kubernetes
#196Kubernetes seems like an "acquired taste". Either you use it a lot (likely at work) and are therefore comfortable using it outside of work as your one-size-fits-all solution to everything, or else you don't use it a lot and see it as a complexity behemoth that hides all of your system behind esoteric CLIs and config files that just make everything a nightmare to manage.
Building self healing server clusters that:
-can run any workload
-on any hardware
-at any scale
-with load balancers
-and persistent disks
-and auto scaling
-and resource limits
-and certificate management
-and no single point of failure
-and etc.