-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Doc] Add NFS-on-Longhorn documentation #1183
Comments
Depends on the result of #1105 |
We need a test plan for NFS. Ideally, we should test it end to end for the workload cases. |
Pre-merged Checklist
|
One additional thing to consider is when after we implement #1470 , it should be easy for the user to upgrade. My biggest concern is if the user can use the same StorageClass name |
Validation - Passed Followed the docs https://staging.longhorn.io/docs/1.0.0/advanced-resources/rwx-workloads/ example workloads are coming up healthy properly. RWX functionality is working fine. |
This is great! Except that I've now spent a lot of time extracting the state out of some apps into s3/minio (+redis for some things) and you suddenly give me an easier way. FWIW, I did try NFS provisioner on-top of a longhorn volume, and I had some inconsistent results. e.g. I STILL have a stuck pod on a production cluster that cannot be removed for some reason and it was part of that experiment. I will try the longhorn built in when ready. |
@jaredkipe Was this using the longhorn provided nfs-provisioner deployments that will be released with 1.0.1? |
@joshimoo No, I mean like a year ago on one cluster and 6 months ago on another. |
@khushboo-rancher added a tracking issue for the e2e integration tests #1606 can you close this issue? |
i## Highlights: 1. [Make Longhorn Helm Chart directly available through Helm repo](longhorn#1043). Now the users can use `helm repo add longhorn https://charts.longhorn.io` to find and install Longhorn easily through Helm command line. 1. [NFS on Longhorn for RWX Access Mode (experimental)](longhorn#1183). We've provided a way to add Longhorn backed NFS provisioner to the cluster, so now user can use `longhorn-nfs` StorageClass to provision RWX volumes. Note: currently NFS provisioner is not highly available. If the node NFS provisioner running is down, the workload using RWX volume might be interrupted for a couple of minutes before restoring the service. Check [here](https://staging.longhorn.io/docs/1.0.0/advanced-resources/rwx-workloads/) for details. 1. Improved Air Gap Environment Support. Check [here](https://staging.longhorn.io/docs/1.0.0/advanced-resources/deploy/airgap/) for updated document for air gap installation. 1. [Remove the air gap image name length limitation](longhorn#1323). 1. [Change the default image pull policy from `Always` to `IfNotPresent`](longhorn#1491) 1. [Aggregate the necessary Docker images](longhorn#1419) 1. [HTTP/HTTPS_PROXY support for S3 backupstore](longhorn#1540) 1. [Support PriorityClass for Longhorn deployment](longhorn#1487). Check [here](https://staging.longhorn.io/docs/1.0.0/advanced-resources/deploy/priority-class/) for details. Live upgrade from v1.0.0 to v1.0.1 is supported. Signed-off-by: Sheng Yang <sheng.yang@rancher.com>
i## Highlights: 1. [Make Longhorn Helm Chart directly available through Helm repo](#1043). Now the users can use `helm repo add longhorn https://charts.longhorn.io` to find and install Longhorn easily through Helm command line. 1. [NFS on Longhorn for RWX Access Mode (experimental)](#1183). We've provided a way to add Longhorn backed NFS provisioner to the cluster, so now user can use `longhorn-nfs` StorageClass to provision RWX volumes. Note: currently NFS provisioner is not highly available. If the node NFS provisioner running is down, the workload using RWX volume might be interrupted for a couple of minutes before restoring the service. Check [here](https://staging.longhorn.io/docs/1.0.0/advanced-resources/rwx-workloads/) for details. 1. Improved Air Gap Environment Support. Check [here](https://staging.longhorn.io/docs/1.0.0/advanced-resources/deploy/airgap/) for updated document for air gap installation. 1. [Remove the air gap image name length limitation](#1323). 1. [Change the default image pull policy from `Always` to `IfNotPresent`](#1491) 1. [Aggregate the necessary Docker images](#1419) 1. [HTTP/HTTPS_PROXY support for S3 backupstore](#1540) 1. [Support PriorityClass for Longhorn deployment](#1487). Check [here](https://staging.longhorn.io/docs/1.0.0/advanced-resources/deploy/priority-class/) for details. Live upgrade from v1.0.0 to v1.0.1 is supported. Signed-off-by: Sheng Yang <sheng.yang@rancher.com>
As a user of Longhorn, I would like to know how I can help support the applications I deploy that require RWX. It has been brought to my attention that running an NFS layer atop longhorn will facilitate that type of use case. Can we add supporting documentation to help walk through users in the setup of this approach?
The text was updated successfully, but these errors were encountered: