Longhorn VS OpenEBS

I'm looking forward to Longhorn[1] taking advantage of this technology. [1]: https://github.com/longhorn/longhorn. - Source: Hacker News / 5 months ago

What backup store you were using? S3 or NFS? Have you tried to report your issues to https://github.com/longhorn/longhorn? Longhorn maintainers/contributors will definitely help with any issues reported by the community. Source: 11 months ago

ChubaoFS - distributed file system and object storage Longhorn - Cloud-Native distributed block storage built on and for Kubernetes OpenEBS - Kubernetes native - hyperconverged block storage with multiple storage engines Rook - Storage Orchestration for Kubernetes SeaweedFS - Distributed file system supports read-write many volumes TiKV - Distributed transactional key-value database Velero - Backup... - Source: dev.to / over 2 years ago

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. [0]:... - Source: Hacker News / over 2 years ago

Feel free to reach out to us in CNCF Slack channel #longhorn or Rancher user slack channel #longhorn-storage, or file an issue in github.com/longhorn/longhorn . We've dedicated engineers every week to help the community members. Source: almost 3 years ago

Last few months I experimented more and more with all OpenEBS solutions that fit small Kubernetes cluster, using MicroK8S and Hetzner Cloud for a real experience. - Source: dev.to / over 1 year ago

I would investigate https://openebs.io/ https://portworx.com/ https://longhorn.io/ if you are forced to you can mount ISCSI on the kublet and feed it to one of those solutions. Keep in mind most of the big guys buy some sort of managed solution that you can point a CSI like trident https://netapp-trident.readthedocs.io. Source: almost 2 years ago

What are some cool projects to self hosted on a home Raspberry Pi (64 bit) Kubernetes cluster (Helm charts). Arm64 support is a must. A lot of projects only build amd64 Docker containers which don't run on my cluster. I currently run:

   - obenebs (provides abstraction for using local k8s worker disks as PVC mounts when running on-prem) -- https://openebs.io/.

- Source: Hacker News / about 2 years ago

What do you use to provision Kubernetes persistent volumes on bare metal? I’m looking at open-ebs (https://openebs.io/). Also, when you bump the image tag in a git commit for a given helm chart, how does that get deployed? Is it automatic, or do you manually run helm upgrade commands? - Source: Hacker News / over 2 years ago

Ideas from my kubernetes experience: * Cert-Manager is very popular and almost a must-have if you terminate SSL inside the cluster * Backups using velero * A dashboard/UI is actually very helpful to quickly browse resources, client tools like k9s are fine too * Secret: Management: Bitnami Sealed Secrets is the second big project in that space * I would add Loki to aggregate Logs * Never heard of ory. Usually I see... Source: over 2 years ago