fluid-addon

fluid-addon is an addon that integrates the fluid project into OCM.

Install the fluid-addon to the Hub cluster

Switch context to Hub cluster.

$ kubectl apply -f deploy/addon

You can check if the fluid addon was deployed by:

$ kubectl get clustermanagementaddon fluid
$ kubectl get addontemplate fluid-0.0.1

Enable the fluid addon for a managed cluster

By default, all the managed clusters selected by the placement placement-all will have the fluid addon enabled with the default configuration.

If you want to enable the addon on GKE clusters, use the placement-gke to select your GKE clusters. Then GKE specific configuration will be applied to the managed clusters selected by the placement placement-gke.

If you want to enable the addon on OCP clusters, use the placement-ocp to select your OCP clusters. Then OCP specific configuration will be applied to the managed clusters selected by the placement placement-ocp. NOTE: Enable the fluid addon on OCP clusters is still work-in-progress. but here are some notable points that are reqquired for the OCP SecurityContextConstraints:

• use oc adm policy add-scc-to-user anyuid -z fluid-webhook -n fluid-system to allow the fluid-webhook to run as anyuid;
• Custimize a SecurityContextConstraints, then use oc adm policy add-scc-to-user fluid-scc -z fluid-csi -n fluid-system to grant the fluid-csi necessary permissions;

If you want to enable the fluid addon for a specific managed cluster, you can change the .spec.installStrategy in the clusterManagementAddon to type: Manual, then apply a managedclusteraddon to enable the fluid for a managed cluster(eg cluster1) by the tool clusteradm cli:

clusteradm addon enable --names=fluid --clusters=cluster1

You can check if the fluid addon was enabled by:

$ kubectl -n cluster1 get managedclusteraddon fluid # Replace 'cluster1' with the managed cluster name
NAME    AVAILABLE   DEGRADED   PROGRESSING
fluid   True                   False

Verify the fluid components are installed on the Managed cluster

Switch context to the Managed cluster.

$ kubectl get pod -n fluid-system
NAME                                     READY   STATUS      RESTARTS   AGE
csi-nodeplugin-fluid-bw4qv               2/2     Running     0          16m
dataset-controller-64cf69f489-hcx7s      1/1     Running     0          16m
fluid-crds-upgrade-0.9.2-02f70ac-w7tft   0/1     Completed   0          16m
fluid-webhook-5998fb4c9-bxmxt            1/1     Running     0          16m
fluidapp-controller-6c59d668cf-pxhjc     1/1     Running     0          16m

Verify the fluid addon is functioning

As a Managed cluster admin

Switch context to the Managed cluster.

Please refer to the Get Started of the fluid doc to crate a dataset to verify that the fluid is functioning properly.

As a Hub cluster admin

Switch context to the Hub cluster. Distribute fluid resources by manifestworks to the managed cluster.

# clusteradm create work dataset-demo -c cluster1 -f quick-start/dataset.yaml
# clusteradm create work runtime-demo -c cluster1 -f quick-start/runtime.yaml
# clusteradm create work app-demo -c cluster1 -f quick-start/app.yaml