longhorn
loki
Our great sponsors
longhorn | loki | |
---|---|---|
59 | 58 | |
4,404 | 18,133 | |
2.4% | 1.1% | |
8.3 | 9.8 | |
4 days ago | 6 days ago | |
Shell | Go | |
Apache License 2.0 | GNU Affero General Public License v3.0 |
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.
longhorn
-
Just finished migrating my old tower servers to a Kubernetes cluster on my new rack!
For my primary CSI provider, I use Longhorn, and to administrate my clusters, I use the Kubernetes Dashboard. In front of all of my private dashboards, I use Traefik Forward Auth to limit who can access them.
-
NAS on a cluster
Maybe with https://longhorn.io
-
TopoLVM to provide local storage
For data must be protected, I use Longhorn https://longhorn.io/ which is basically iSCSI/NFS with replication.
-
Homelab and Long Term Data Integrity?
Backups are definitely necessary. The problem though is that you cant detect by default if you are backing up corrupted data. By now i found three approaches: 1. Use a filesystem that detects and fixes errors (e. g. btrfs or zfs) 2. Use par2 (parchive) to generate checksums on your files manually 3. I found the following issue on the k8s storage solution I currently use: https://github.com/longhorn/longhorn/issues/3198 For now I am waiting for option 3 getting merged. In the long run I will upgrade my laptop to btrfs and for now use par2. Hope that provides a starting point. Feel free to add your ideas!
-
Change SSH port
You can use the Longhorn iSCSI installer script as an example. https://github.com/longhorn/longhorn/blob/master/deploy/prerequisite/longhorn-iscsi-installation.yaml
-
Learning with K3s at home. "Best" storage option for a single-node cluster?
Rancher's Longhorn (even though it's only a single-node)
-
Running Kubernetes cluster locally to self host a bunch of applications along with a DNS server
Application storage now: yes, NAS is probably the best way to go about it. I believe k3s uses some kind of "local storage" by default but there's plenty of alternative Container Storage Interfaces (CSI) out there. Longhorn worked well for me and it covers most uses cases I care about: snapshots, backups, and replication. I don't know about any "NAS providers" though, and once again there will be performance drawbacks with having your storage that externalized.
-
Advice on system design best practices?
For me longhorn works really well as my storage backend.
-
Install and configure a high available Kubernetes cluster with Ansible
Longhorn is a lightweight, reliable, and powerful distributed block storage system for Kubernetes.
-
What selfhosted packages are you using?
You mentioned storage... That's always tricky but provisioning persistent volumes with https://longhorn.io is really simple... It's also easy to setup, the helm chart is wonderful
loki
-
Log monitoring open source tool for prometheus
Like all the top posts here say, you're going to want Loki. Probably Promtail to collect logs and push them to Loki (although any log collector works..I've also used Fluentd, Fluent-bit, and logstash). Setup a data source in Grafana and it works great. I install all of them from Grafana's own helm charts: https://github.com/grafana/loki/tree/main/production/helm
-
Splunk IP suit against Cribl
> Is there an open source version of splunk I can modify?
https://github.com/grafana/loki might work for you. It’s not a drop in replacement for Splunk, FWIW.
- ZincSearch – lightweight alternative to Elasticsearch written in Go
- Think Prometheus, but for logs (not metrics). Simple, efficient, fast log store
- Ask HN: IT Security Checklist for Startups?
-
Thoughts on Opentelemetry?
OP specifically mentioned APM, which is what maps to Tempo. If you wanted to go full Grafana for metrics and logs too, you can add in Mimir and Loki
-
Kubernetes cluster using Raspberry Pis with basic services (Storage,Logging, Monitoring, Backup). Building guides and automation with Ansible.
I notice that Loki's treadme says it doesn't index log content. I don't know at what scale that becomes an issue. Have you had any performance concerns?
Similarly, fluentd is much more like NoSQL as a datastore than anything else. Prometheus is fundamentally a TSDB, and Loki is moving that direction (it's currently boltdb, which is also just a k:v store).
-
Log Central
I don't quite understand the window-logic but for logs there are things like Logstash, Loki, Graylog and probably many others that are meant to handle logs.
What are some alternatives?
rook - Storage Orchestration for Kubernetes
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
ClickHouse - ClickHouse® is a free analytics DBMS for big data
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
zfs-localpv - CSI Driver for dynamic provisioning of Persistent Local Volumes for Kubernetes using ZFS.
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
loki-multi-tenant-proxy - Grafana Loki multi-tenant Proxy. Needed to deploy Grafana Loki in a multi-tenant way
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
cortex - A horizontally scalable, highly available, multi-tenant, long term Prometheus.
ElastiFlow - Network flow analytics (Netflow, sFlow and IPFIX) with the Elastic Stack
Typesense - Open Source alternative to Algolia and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences