K3s
Reddit take
Not enough linked mention summaries yet; the source excerpts below are the evidence.
Pros
- If you plan to use something like longhorn for pvc creation then k3s would be better cause it’s lighter
- Just migrated mine to k3s too! (K3s because it can easily integrate with tailscale)
- Since your workloads are already containerized, I'd suggest to try out k3s (or any other Kubernetes implementation), and set up a ZFS pool (or pools) for storage. Much less overhead than full-blown virtualization, yet similarly easy to s...
- if you have time and your keen do Kubernetes (k8s) I recommend looking into the slimmed down version k3s, if a container starts to fail or fails another will automatically be spun up so services continue ☺️
- Parent context: Maybe look at k3s it has less overhead and is easier to manage at a low number of nodes Reply: You are completely right, working with k3s is easy and takes little time to set up.
Cons
- Does anyone here run K3s on top of Proxmox? I’m trying to figure out the best way to automatically join a Proxmox VM to my K3s cluster on creation.
- K3S on Ubuntu, managed via Portainer: This was easy to install, but everything is totally foreign to me here. I've been able to spin up a few containers, but the vast majority of the ones there are helm charts are related to managing kub...
- Now, I plan to install K3s to orchestrate my applications and get my hands dirty on Kubernetes.
- Hoping to switch to K3s in the next few months.
Sentiment
11 positive (73%) · 3 mixed (20%) · 1 negative (7%)
Trust + time weighted score: +71% · raw score 67%
What redditors said (10 of 15)
If you plan to use something like longhorn for pvc creation then k3s would be better cause it’s lighter
Just migrated mine to k3s too! (K3s because it can easily integrate with tailscale)
Does anyone here run K3s on top of Proxmox? I’m trying to figure out the best way to automatically join a Proxmox VM to my K3s cluster on creation.
Since your workloads are already containerized, I'd suggest to try out k3s (or any other Kubernetes implementation), and set up a ZFS pool (or pools) for storage. Much less overhead than full-blown virtualization, yet similarly easy to snapshot, back up or reinstall from zero.
if you have time and your keen do Kubernetes (k8s) I recommend looking into the slimmed down version k3s, if a container starts to fail or fails another will automatically be spun up so services continue ☺️
Parent context: Maybe look at k3s it has less overhead and is easier to manage at a low number of nodes Reply: You are completely right, working with k3s is easy and takes little time to set up.
I do- recommend rancher + k3s. Lightweight, reliable, easy to maintain and update.
Maybe look at k3s it has less overhead and is easier to manage at a low number of nodes
If it's just the application side then I would suggest a managed solution like k3s/microk8s/k8s for simplicity and your sanity.
K3S on Ubuntu, managed via Portainer: This was easy to install, but everything is totally foreign to me here. I've been able to spin up a few containers, but the vast majority of the ones there are helm charts are related to managing kubernetes, not actually doing anything useful.