Skip to content

Latest commit

 

History

History
165 lines (122 loc) · 6.18 KB

install.md

File metadata and controls

165 lines (122 loc) · 6.18 KB
Raw

Deploy Fluid on Your Kubernetes Cluster

Prerequisites

  • Git
  • Kubernetes cluster（version >= 1.16）, and support CSI
  • kubectl（version >= 1.16）
  • Helm（version >= 3.5）

The following documents assume that you have installed all the above requirements.

For the installation and configuration of kubectl, please refer to here.

For the installation and configuration of Helm 3, please refer to here.

How to Deploy

Download Fluid Chart

You can download the latest Fluid installation package from Fluid Releases.

Install Fluid with Helm

Create namespace:

$ kubectl create ns fluid-system

Install Fluid with:

$ helm install fluid fluid.tgz
NAME: fluid
LAST DEPLOYED: Fri Sep  2 19:03:56 2022
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

For Kubernetes version lower than v1.17(included), please use helm install --set runtime.criticalFusePod=false fluid fluid.tgz

The general format of the helm install command is like: helm install <RELEASE_NAME> <SOURCE>. In the above command, the first fluid means the release name, and the second fluid specified the path to the helm chart, i.e. the directory just unpacked.

Upgrade Fluid to the latest version(v0.8) with Helm

If you have installed an older version of Fluid before, you can use Helm to upgrade it. Before upgrading, it is recommended to ensure that all components in the AlluxioRuntime resource object have been started completely, which is similar to the following state:

$ kubectl get pod
NAME                 READY   STATUS    RESTARTS   AGE
hbase-fuse-chscz     1/1     Running   0          9h
hbase-fuse-fmhr5     1/1     Running   0          9h
hbase-master-0       2/2     Running   0          9h
hbase-worker-bdbjg   2/2     Running   0          9h
hbase-worker-rznd5   2/2     Running   0          9h

upgrade fluid：

$ helm upgrade fluid fluid/
Release "fluid" has been upgraded. Happy Helming!
NAME: fluid
LAST DEPLOYED: Fri Sep  2 18:54:18 2022
NAMESPACE: default
STATUS: deployed
REVISION: 2
TEST SUITE: None

For Kubernetes version lower than v1.17(included), please use helm install --set runtime.criticalFusePod=false fluid fluid.tgz

We recommend you to update Fluid v0.8 from v0.7. If you have an older version, our suggestion is to reinstall it to ensure everything works fine.

Check Status of Component

Check CRD used by Fluid:

$ kubectl get crd | grep data.fluid.io
alluxioruntimes.data.fluid.io                          2022-06-28T02:43:52Z
databackups.data.fluid.io                              2022-06-28T02:43:52Z
dataloads.data.fluid.io                                2022-06-28T02:43:52Z
datasets.data.fluid.io                                 2022-06-28T02:43:52Z
goosefsruntimes.data.fluid.io                          2022-06-28T02:43:52Z
jindoruntimes.data.fluid.io                            2022-06-28T02:43:52Z
juicefsruntimes.data.fluid.io                          2022-06-28T02:43:52Z

Check the status of pods:

$ kubectl get pod -n fluid-system
NAME                                        READY   STATUS      RESTARTS   AGE
csi-nodeplugin-fluid-g6ggh                  2/2     Running     0          6m53s
csi-nodeplugin-fluid-tnj5r                  2/2     Running     0          5m50s
dataset-controller-5f56cc4f97-2lfqt         1/1     Running     0          6m54s
fluid-crds-upgrade-0.8.0-aa7fdca--1-gtpt9   0/1     Completed   0          7m23s
fluid-webhook-7d8c586f59-mxkwz              1/1     Running     0          6m54s
fluidapp-controller-86f5bfc4c5-ct25p        1/1     Running     0          6m54s

If the Pod status is as shown above, then Fluid is installed on your Kubernetes cluster successfully!

Check version info of Component

When csi-nodeplugin, alluxioruntime-controller and dataset-controller start，they will print their own version info into logs.
If you installed with the charts provided by us，their version info will be fully consistent.
If you installed manually, their version info may be not consistent. You can check it with the following command:

$ kubectl exec csi-nodeplugin-fluid-pq2zd -n fluid-system -c plugins fluid-csi version
$ kubectl exec alluxioruntime-controller-66bf8cbdf4-k6cxt -n fluid-system -- alluxioruntime-controller version
$ kubectl exec dataset-controller-558c5c7785-mtgfh -n fluid-system -- dataset-controller version

The output should be like:

  BuildDate: 2022-09-01_13:07:33
  GitCommit: aa7fdca4c4306762280570b7dc0c2a7c649ff785
  GitTreeState: clean
  GoVersion: go1.17.8
  Compiler: gc
  Platform: linux/amd64

Fluid use cases

For more use cases about Fluid, please refer to our demos:

Uninstall Fluid

To uninstall fluid safely, we should check weather Custom Resource Objects about fluid have been deleted completely first:

kubectl get crds -o custom-columns=NAME:.metadata.name | grep data.fluid.io  | sed ':t;N;s/\n/,/;b t' | xargs kubectl get --all-namespaces

If you confirm that all Custom resource objects about fluid have been deleted, you can safely uninstall fluid:

$ helm delete fluid
$ kubectl delete -f fluid/crds
$ kubectl delete ns fluid-system

The fluid in command helm delete means the <RELEASE_NAME> during installation.

Advanced Configuration

  1. In some cloud vendors, the default mount root directory /runtime-mnt is not writable, so you have to modify the directory location
helm install fluid --set runtime.mountRoot=/var/lib/docker/runtime-mnt fluid
  1. The feature Fuse Recovery is not enable by default, to enable this:
helm install fluid --set csi.featureGates='FuseRecovery=true' fluid