|6 days ago||about 14 hours ago|
|Apache License 2.0||The Unlicense|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Is there any way to exclude new nodes to a K3S cluster from being longhorn storage nodes?
1 project | reddit.com/r/rancher | 3 Dec 2021
You can use node selector rules to force Longhorn to use some nodes for storage. You can also add taints to create dedicated storage nodes. Please see the GitHub link listed below. https://github.com/longhorn/longhorn/issues/1633
Separating storage and worker nodes with Longorn
1 project | reddit.com/r/rancher | 25 Nov 2021
In Longhorn GUI the volume shows as Detached. It would attach if I do is manually but that makes no impact to the Pod. I've seen people having similar issues in 2614 and have tried with create-default-disk-on-labeled-nodes but that does not seem to work the way I would like to. If I deploy without nodeSelector and disable scheduling on worker nodes it works fine.
Building a "complete" cluster locally
24 projects | reddit.com/r/kubernetes | 31 Oct 2021
rook/longhorn for distributed storage
Dynamic storage class in K3s on docker
2 projects | reddit.com/r/kubernetes | 15 Oct 2021
Longhorn is exactly what you're looking for. It's easy to set up and backs up to NFS.
Rancher Desktop, a Docker Desktop Replacement
14 projects | news.ycombinator.com | 11 Oct 2021
More than performance, I am worried about security. They don't seem to have considered it at all when building it: https://github.com/longhorn/longhorn/issues/1983
Probably not a good recommendation until this hole is plugged.14 projects | news.ycombinator.com | 11 Oct 2021
They've also got Longhorn, a distributed container-attached storage solution that's very simple to understand and easy to deploy. Performance is another thing but that's the same with all of the general networked storage solutions (Ceph included).
Rancher's got a well deserved good impression in my mind, though early on I avoided it since it seemed like they were building a walled garden.
Should We Replace Docker Desktop With Rancher Desktop?
6 projects | reddit.com/r/kubernetes | 11 Oct 2021
All of their projects have been fully open, monetized with enterprise support. They straight up fully donated their storage project to the CNCF. They've been good stewards of all the tools so far with ones like k3s greatly benefitting the community. And have put a decent amount of effort into putting resources supporting issues on even non-paid issues on the GitHub projects.
ZFS and Ceph
2 projects | reddit.com/r/zfs | 22 Sep 2021
Also just in case the above wasn't enough I'm probably actually going to run Longhorn because it's just SO much easier than Ceph to manage and gives me the availability for a ~40% perf loss AFAIK.
Those running Kubernetes, what is in your core stack? And what "gem" can you not live without?
8 projects | reddit.com/r/homelab | 19 Sep 2021
Longhorn for Kubernetes storage. It lets me automatically provision PersistentVolumes and snapshot/back them up to S3. I've read that other things such as Ceph and Rook are more stable and I've definitely been bit by some non-critical bugs, but the project is very active and bugs are squashed quickly (though they don't release very frequently). This is the gem I can't live without, being able to snapshot, backup and restore things like my Plex volume has saved me at least a dozen times already.
Selfhosted storage recommendation
1 project | reddit.com/r/selfhosted | 18 Sep 2021
Another consideration is using something like https://longhorn.io/, it's a bit like ceph, and supports mirroring over two nodes
Kubernetes best practices generally and for organizing my stuff
2 projects | reddit.com/r/selfhosted | 24 Apr 2021
Check out Flux V2. It syncs a git repo with your cluster, allowing you to define your infrastructure as code. It will keep your cluster synced with your repo and detect changes. A number of example repos are Here and onedr0p did a example repo here There's many options for structuring folder, I'd recommend you have a look at a few repos and pick one you like. The linked template is a good start, as it helps avoid dependency hell with a crd folder that starts before the YAML that needs the crd defined. Many people on the awesome list also run ansible for full infrastructure as code. I spent a lot of time perfecting my setup to go from blank Ubuntu VM to my cluster with a few keystrokes. Running it in git also helps you be able to use things like renovate bot to keep versions up to date. As for namespaces, everyone had their own method, but about using kube-system. Also, keep a eye out for services that refuse to have their name space changed.
How did you really master Kubernetes?
4 projects | reddit.com/r/kubernetes | 23 Apr 2021
This is more of less the exact path I took when diving in. I usually like to dog food anything I'm planning to use professionally and what helped alot was attempting to port my home stuff over to the k8s world. I use to have home assistant running in my house on a single RPI and it's evolved into a SOPS managed k8s cluster of NUCs easily deployable and git tracked. +1 on skipping helm charts initially, you add time but you learn alot more about what's going on under the hood manually piecing those deployments initially. One important thing is also considering upgrade strategies of all the things. Once you put something in the wild and it's used by others, that can quickly become a PITA. I'd recommend at some point in the investigation checking out https://github.com/k8s-at-home/awesome-home-kubernetes too, which is a great (awesome?) list of git ops managed k8s clusters in their community. They recently released a template that will let you bootstrap a k3s cluster tied it to a git repo that lets to leverage simple CI to action deployments to your cluster.
Created a k3s cluster server with Raspberry Pis, What is next?
3 projects | reddit.com/r/kubernetes | 15 Apr 2021
Take a look at https://github.com/k8s-at-home/awesome-home-kubernetes for ideas, https://github.com/k8s-at-home/charts for some "home" focused helm charts, and https://discord.gg/Yv2gzFy for any help with the charts or running k8s-at-home.
The Decline of Heroku
4 projects | news.ycombinator.com | 12 Apr 2021
huge fan of k8s. drop what you're doing & use a cross-system object-storage/"apiserver" & control-loops to automate everything; embrace desired state management & thank me latter. but, Heroku &al have a lot of value left.
there's just not that many folk trying to tame deploys on k8s via gitops. flux2 is the rage, it's all over the alpha geek's efforts, but it's usually used by someone carefully authoring a fairly complex Helm file, then building out a significant Flux2 HelmRelease object (ex: ).
there's a bunch of other tools, & i'm frankly not familiar enough. but this idea of having a bunch of source that can deploy itself, simply, is still extremely rare even among the alpha-geek #gitops types. i'm sure some of these tools better match the simplicity of the Heroku model, corresponding branches to environments, which makes so so much sense, but so far i feel like such attempts are still basically unknown.
heroku's really simmered it down to something that made extremely natural sense. huge props to that. too too much of this effort had to go into creating buildpacks & supporting language environments very very carefully very actively, that ability to stealth-containerize an app & not even notice is so much of the special sauce that makes this a hard, hard & eternal problem (because langauges/envs keep changing). there's still a lot of ease of use to Heroku that's potentially will be underrated and/or lost by the oncoming generations. i have high respect for how operateable Heroku is.
Unironically Using Kubernetes for My Personal Blog
12 projects | news.ycombinator.com | 18 Mar 2021
> There isn't any gain for home networking. The gain is for enterprise applications that can now migrate a software-defined network to a completely different infrastructure provider without having to change the way they do monitoring, log collection, storage provisioning, DNS migrates with it for free, etc.
This is an unbelievable amount of gate-keeping hogwash. I don't know who this person thinks they can arbitrate what is a good usage & what cases this is too-powerful too-interesting too-useful to bother using it in.
There is so so so much fear & doubt & scare in this post. Screw this gate-keeping crap.
> Maybe, if you're lucky, you had some set of really good and reliable Sys Admins that figured out a robust way to script and configure the setup process of your original on-premise data center and they captured that in very good, well-maintained documentation. If you're even luckier, maybe those same guys still work for you.
"Only us good right & virtuous & amazing engineers can handle this! This is too pure, too amazing for mortals! They're wasting their time! They'll get the configuration wrong! They're bad people. Only professionals are qualified to play with Kubernetes!"
UGH ENOUGH. Stop this terrible attitude. This is so down-talk-y.
Please don't assume, please don't dictate your limited terms to the world. Let the world try. Let us not be cowed, & afraid, to use good tech, by these scare words.
As it turns out, it's just not that hard. It's a better environment, a better world. There are lots of home users using Kubernetes. It doesn't take a colossal investment. It's fairly secure out of the box, at least if you're not trying to run a multi-tenant home.
See? Look. Lots of projects: https://github.com/k8s-at-home/awesome-home-kubernetes . Lots. Good people, just trying. Not taking the poison words to be afraid, that this is too hard.
"For one person, this means nothing. This guy is just doing it for fun. "
What a BAD ATTITUDE. Snarking & being mean, to people out there, trying to find better ways to do things, to create shared, meaningful value. With good, autonomic systems. With reasonably competent free-to-everyone utility scale / cloud computing. Don't accept such words as these. Do not be afraid to involve yourselves. Do not be gate-kept like this. Run Kubernetes. Run good systems. Stop being sold on second, third run systems. You are not saving yourselves any hardship. You can run K3S in <20 minutes, and you can start loading amazing Charts seconds after. Please allow yourself a moment of un-doubt where you consider, maybe, this has amazing value for the home, that it's already possibly incredibly robust, please consider that applying some manifests might be super easy. Please consider that blog posts are the canonical way to share work, before Kubernetes, but now I can link you to a repo full of people sharing manifests & charts & works, that stand a decent chance of running on any cloud or at home. There's a lot of sophisticated under-the-hood boons to running Kubernetes too, but as for what the home-user gains: it's amazing. And growing.
My notes/guide how I setup Kubernetes k3s, OpenFaaS, Longhorn, MetalLB, Private Docker registry, Redis and more on 9x Raspberry 4 :)
2 projects | reddit.com/r/kubernetes | 7 Feb 2021
Want to transition from docker / portainer to kubernetes
1 project | reddit.com/r/kubernetes | 9 Jan 2021
I can advise you to look at https://github.com/k8s-at-home/awesome-home-kubernetes Join also discord channel which is full of people willing to help
What are some alternatives?
rook - Storage Orchestration for Kubernetes
zfs-localpv - CSI Driver for dynamic provisioning of Persistent Local Volumes for Kubernetes using ZFS.
k3sup - bootstrap Kubernetes with k3s over SSH < 1 min 🚀
k3s - Lightweight Kubernetes
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
loki - Like Prometheus, but for logs.
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
watchtower - A process for automating Docker container base image updates.
template-cluster-k3s - Highly opinionated template for deploying a single k3s cluster with Ansible and Terraform backed by Flux and SOPS.