Update README.md

Update to point to the yaml file from the master branch.

And we will try to keep that stable.
This commit is contained in:
Sheng Yang 2018-03-27 18:10:55 -07:00 committed by GitHub
parent 2ce49a1235
commit b6d3ab2e68
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -31,7 +31,7 @@ Longhorn is 100% open source software. Project source code is spread across a nu
## Deployment
Create the deployment of Longhorn in your Kubernetes cluster is easy. For most Kubernetes setup (except GKE), you will only need to run the following command to install Longhorn:
```
kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/v0.2/deploy/longhorn.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/deploy/longhorn.yaml
```
For Google Kubernetes Engine (GKE) users, see [here](#google-kubernetes-engine) before proceed.
@ -193,7 +193,7 @@ See [here](https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-acc
2. The default Flexvolume plugin directory is different with GKE 1.8+, which is at `/home/kubernetes/flexvolume`. User need to use following command instead:
```
kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/v0.2/deploy/longhorn-gke.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/deploy/longhorn-gke.yaml
```
User can also customerize the Flexvolume directory in the last part of the Longhorn system deployment yaml file, e.g.:
@ -213,7 +213,7 @@ kubectl -n longhorn-system delete lhv --all
After confirming all the volumes are removed, then Longhorn can be easily uninstalled using:
```
kubectl delete -f https://raw.githubusercontent.com/rancher/longhorn/v0.2/deploy/longhorn.yaml
kubectl delete -f https://raw.githubusercontent.com/rancher/longhorn/master/deploy/longhorn.yaml
```
## Troubleshooting