longhorn | Cloud-Native distributed storage built on and for Kubernetes | Storage library

by longhorn Shell Version: v1.5.0-rc2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(8)Vulnerabilities Install Support

kandi X-RAY | longhorn Summary

longhorn is a Shell library typically used in Storage applications. longhorn has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Longhorn is a distributed block storage system for Kubernetes. Longhorn is cloud native storage because it is built using Kubernetes and container primitives. Longhorn is lightweight, reliable, and powerful. You can install Longhorn on an existing Kubernetes cluster with one kubectl apply command or using Helm charts. Once Longhorn is installed, it adds persistent volume support to the Kubernetes cluster.

Support

Quality

Security

License

Reuse

Support

longhorn has a medium active ecosystem.

It has 4763 star(s) with 613 fork(s). There are 96 watchers for this library.

There were 5 major release(s) in the last 12 months.

There are 1046 open issues and 3903 have been closed. On average issues are closed in 70 days. There are 14 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of longhorn is v1.5.0-rc2

Quality

longhorn has 0 bugs and 0 code smells.

Security

longhorn has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

longhorn code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

longhorn is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

longhorn releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

It has 87 lines of code, 8 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of longhorn

Get all kandi verified functions for this library.

longhorn Key Features

No Key Features are available at this moment for longhorn.

longhorn Examples and Code Snippets

No Code Snippets are available at this moment for longhorn.

Community Discussions

Trending Discussions on longhorn

Longhorn using more than 50% of storage as reserved space

Bind kubernetes istio ingress gateway to local ports 80 and 443

How to select records Composite Primary key and Foreign key reference (many to many relationship)

Ingress for ECK Elasticsearch not working - 502 gateway

Longhorn backup/snapshot hooks

How to deploy helm chart (that are stored as images) using Ansible?

Node Red on my k3 cluster using YAML not working

How can I retain a PersistenceVolume in Longhorn

QUESTION

Longhorn using more than 50% of storage as reserved space

Asked 2022-Jan-17 at 12:28

I'm running Longhorn v1.2.3 on RKE1 cluster (provisioned by rancher), this cluster has 5 nodes with dedicated 20GiB disks mounted on /var/lib/longhorn, with ext4 filesystem and 0% reserved blocks for root user/group.

In the dashboard, i see the following stats:

Type Size Schedulable 33.5 Gi Reserved 58.1 Gi Used 6.18 Gi Disabled 0 Bi Total 97.8 Gi

I changed Storage Minimal Available Percentage in settings to 5 (from 25 as i recall), but that haven't changed anything. When i open "nodes" tab, i see the following in "Size" tab:

...

ANSWER

Answered 2022-Jan-17 at 12:28

After digging deeper and finding that it was one day possible to adjust these values from UI (i wasn't able to find it), i've searched for longhorn CRDs, and came across nodes.longhorn.io. And inside definition i've found exactly what i searched for:

Source https://stackoverflow.com/questions/70741359

QUESTION

Bind kubernetes istio ingress gateway to local ports 80 and 443

Asked 2021-Dec-15 at 12:14

I managed to install kubernetes 1.22, longhorn, kiali, prometheus and istio 1.12 (profile=minimal) on a dedicated server at a hosting provider (hetzner).

I then went on to test httpbin with an istio ingress gateway from the istio tutorial. I had some problems making this accessible from the internet (I setup HAProxy to forward local port 80 to the dynamic port that was assigned in kubernetes, so port 31701/TCP in my case)

How can I make kubernetes directly available on bare metal interface port 80 (and 443).

I thought I found the solution with metallb but I cannot make that work so I think it's not intended for that use case. (I tried to set EXTERNAL-IP to the IP of the bare metal interface but that doesn't seem to work)

My HAProxy setup is not working right now for my SSL traffic (with cert-manager on kubernetes) but before I continue looking into that I want to make sure. Is this really how you are suppose to route traffic into kubernetes with an istio gateway configuration on bare metal?

I came across this but I don't have an external Load Balancer nor does my hosting provider provide one for me to use.

...

ANSWER

Answered 2021-Dec-14 at 09:31

Posted community wiki answer for better visibility based on the comment. Feel free to expand it.

The solution for the issue is:

I setup HAProxy in combination with Istio gateway and now it's working.

The reason:

I think the reason why SSL was not working was because istio.io/latest/docs/setup/additional-setup/gateway creates the ingress gateway in a different namespace (istio-ingress) from the rest of the tutorials (istio-system).

Source https://stackoverflow.com/questions/70247196

QUESTION

How to select records Composite Primary key and Foreign key reference (many to many relationship)

Asked 2021-Sep-16 at 08:44

I am tyring to learn composite Primary Key and Foregin Key. Wherein I am trying to have many to many mappings. Have three tables here.

...

ANSWER

Answered 2021-Sep-16 at 08:44

you can write query without join but need condition in "Where", like that:

Source https://stackoverflow.com/questions/69204985

QUESTION

Ingress for ECK Elasticsearch not working - 502 gateway

Asked 2021-Aug-24 at 21:22

I'm using ECK 1.5.0 and I have to use Ingress to expose Elasticsearch. But I'm getting a 502 gateway when I go to the url (http://my-db-url.com). I have confirmed the database is running fine and able to collect / display data.

I was only able to find solutions to exposing Kibana with Ingress on the web but those were not working for me.

Heres my elasticsearch.yaml (contains Elasticsearch object and Ingress object):

...

ANSWER

Answered 2021-Aug-24 at 21:22

Turns out the same question was asked here: https://discuss.elastic.co/t/received-plaintext-http-traffic-on-an-https-channel-closing-connection/271380

and the solution is to force HTTPS using annotations, which for the nginx ingress controller can be found here: https://github.com/elastic/helm-charts/issues/779#issuecomment-781431675

Source https://stackoverflow.com/questions/68893838

QUESTION

Longhorn backup/snapshot hooks

Asked 2021-Jun-01 at 10:20

How do I configure Longhorn backup so it executes some bash scripts in the pod before and after snapshot/backup is taken?

Something similar to Velero's backup hooks.

...

ANSWER

Answered 2021-Jun-01 at 10:20

Apparently not possible at the moment, according to the longhorn github issue.

You can orchestrate similar behaviour by using volume snapshot

Source https://stackoverflow.com/questions/65630349

QUESTION

How to deploy helm chart (that are stored as images) using Ansible?

Asked 2021-May-12 at 14:16

I have stored the custom made helm charts (Elasticsearch, Longhorn) in the gitlab container registry as images. How can I deploy the helm chart to a kubernetes environment using Ansible?

...

ANSWER

Answered 2021-May-12 at 14:16

There are a lot of Ansible module to deploy a helm charts for example you can follow this links where you can find a lot of example:

I hope that can help you to resolve your issue .

Source https://stackoverflow.com/questions/67502992

QUESTION

Node Red on my k3 cluster using YAML not working

Asked 2021-May-01 at 14:10

I am trying to deploy a simple node-red application to my k3s container. Background I have two pi 4's as my server and 3B+ as my workers.

For errors i get

...

ANSWER

Answered 2021-May-01 at 14:10

For those wondering i got this to work. For some reason it was colliding with the install for node js...No idea why. Uninstalled nodejs and reinstalled and all is working. So nothing wrong with the config file above for those want to use it. Once you bind your config to a volume you can add authentication as well.

Source https://stackoverflow.com/questions/67285801

QUESTION

How can I retain a PersistenceVolume in Longhorn

Asked 2020-Apr-02 at 12:58

I have setup a self managed kubernetes cluster together with longhorn as a distributed storage. The installation was quite simple.

I have created a storage class like this one:

...

ANSWER

Answered 2020-Apr-02 at 12:58

When you delete a PVC, corresponding PV becomes Released. This PV usually contains sensitive data and that is why there is no possibility to bind to it, even if it is a PVC with the same name and in the same namespace as the previous one - who knows who's trying to steal the data!

Admin intervention is required here. There are two options:

Make the PV available to everybody - delete PV.Spec.ClaimRef. This PV can bound to any PVC (assuming that capacity, access mode and selectors match)
Make the PV available to a specific PVC - pre-fill PV.Spec.ClaimRef with a pointer to a PVC. Leave the PV.Spec.ClaimRef and empty UID, as the PVC does not to need exist at this point and you don't know PVC's UID. This PV can be bound only to the specified PVC.

If you are focus on dynamics provisioning usually pvc has static name, because you create it manually, pv's are generated then based on information in claim.

Take a look here: reusing-persistent-volume.

Let me know if it helped.

Source https://stackoverflow.com/questions/60976472

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install longhorn

Engine:
Manager:
Instance Manager:
Share Manager:
Backing Image Manager:
UI:
Test:
Longhorn can be installed on a Kubernetes cluster in several ways:.
Rancher catalog app
kubectl
Helm