Skip to content

Commit

Permalink
Upgrade fluid addon to 1.0.0
Browse files Browse the repository at this point in the history
Signed-off-by: zhujian <jiazhu@redhat.com>
  • Loading branch information
zhujian7 committed Jul 11, 2024
1 parent 94798a7 commit 7d7b09c
Show file tree
Hide file tree
Showing 11 changed files with 6,552 additions and 200 deletions.
20 changes: 19 additions & 1 deletion fluid-addon/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,25 @@ $ kubectl get addontemplate fluid-0.0.1

## Enable the fluid addon for a managed cluster

Then apply a managedclusteraddon to enable the fluid for a managed cluster(eg cluster1) by the tool [clusteradm](https://github.com/open-cluster-management-io/clusteradm/) cli:
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](https://github.com/open-cluster-management-io/clusteradm/) cli:

```
clusteradm addon enable --names=fluid --clusters=cluster1
Expand Down
12 changes: 12 additions & 0 deletions fluid-addon/deploy/addon/addon-deployment-config-gke.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
apiVersion: addon.open-cluster-management.io/v1alpha1
kind: AddOnDeploymentConfig
metadata:
name: fluid-gke-config
namespace: default
spec:
agentInstallNamespace: fluid-system
customizedVariables:
- name: RUNTIME_MOUNT_PATH
value: /tmp/runtime-mnt
- name: CRITICAL_FUSE_POD
value: "false"
12 changes: 12 additions & 0 deletions fluid-addon/deploy/addon/addon-deployment-config-ocp.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
apiVersion: addon.open-cluster-management.io/v1alpha1
kind: AddOnDeploymentConfig
metadata:
name: fluid-ocp-config
namespace: default
spec:
agentInstallNamespace: fluid-system
customizedVariables:
- name: RUNTIME_MOUNT_PATH
value: /tmp/runtime-mnt
- name: CRITICAL_FUSE_POD
value: "true"
12 changes: 12 additions & 0 deletions fluid-addon/deploy/addon/addon-deployment-config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
apiVersion: addon.open-cluster-management.io/v1alpha1
kind: AddOnDeploymentConfig
metadata:
name: fluid-config
namespace: default
spec:
agentInstallNamespace: fluid-system
customizedVariables:
- name: RUNTIME_MOUNT_PATH
value: /runtime-mnt
- name: CRITICAL_FUSE_POD
value: "true"
Loading

0 comments on commit 7d7b09c

Please sign in to comment.