3 ms·
Did you consider MRSK[1], k3s[2], or dokku[3]? They are all significantly simpler to operate than Kubernetes, curious to hear your take. On logs, I agree and h
by ricardobeat 3y ago
Did you consider MRSK[1], k3s[2], or dokku[3]? They are all significantly simpler to operate than Kubernetes, curious to hear your take.
On logs, I agree and have looked for the same. A simple way to aggregate logs in one machine, heck it could even be running SQLite, and query via a web UI. Doesn't seem to exist for this scale.
[1] https://github.com/mrsked/mrsk https://github.com/mrsked/mrsk
[2] https://k3s.io/ https://k3s.io/
[3] https://dokku.com/ https://dokku.com/
- sseagull 3y agoI took a good hard look at dokku , and it almost fits (especially if you put the ledokku web interface in front). I think my main issue was that we have services that have multiple components in a docker compose (not just a webapp + database). These appear awkward for dokku to handle. However, I am still very interested in deploying it, and will revisit in the future. I looked at k3s some, and it is promising. I think overall anything kubernetes related is probably in my future, but I am not familiar enough with the ecosystem to run it in production right now. I did install rancher w/ rke2 and even managed to deploy some of my apps. It's really nice, and runs okay-ish on a single server once you increase the pod limit, but again, not comfortable running it for production (yet). Had never heard of mrsk, but bookmarked for the future. Thanks!
- n3t 3y agoHow can k3s be simpler to operate than Kubernetes when k3s is a Kubernetes distribution?
- ianbutler 3y agok3s is a single binary install that unpacks a lot of k8s parts for you and uses sqlite instead of etcd for the data store. So it's simpler to spin up and manage, not necessarily simpler to use.