Installation

Content Software for File CLI Reference

Version
4.2.x
Audience
anonymous
Part Number
MK-HCSF001-03

From the downloaded location in the Kubernetes master node, run the following command to deploy the Content Software for File CSI Plugin as a DaemonsSet:

$ ./deploy/kubernetes-latest/deploy.sh

On successful deployment, you will see the following output:

creating wekafsplugin 1 namespace
2 namespace/csi-wekafsplugin created
3 deploying wekafs components
4 ./deploy/kubernetes-latest/wekafs/csi-wekafs-plugin.yaml
5 using image: quay.io/k8scsi/csi-node-driver-registrar
6 using image: quay.io/weka.io/csi-wekafs:v0.0.2-25-g7d
7 using image: quay.io/k8scsi/livenessprobe:v1.1.0
8 using image: quay.io/k8scsi/csi-provisioner:v1.6.0
9 using image: quay.io/k8scsi/csi-attacher:v3.0.0-rc1
10 using image: quay.io/k8scsi/csi-resizer:v0.5.0
11 namespace/csi-wekafsplugin configured
12 csidriver.storage.k8s.io/wekafs.csi.k8s.io created
13 serviceaccount/csi-wekafsplugin created
14 clusterrole.rbac.authorization.k8s.io/csi-wekafsplugin-cluster-role cre
15 clusterrolebinding.rbac.authorization.k8s.io/csi-wekafsplugin-cluster-r
16 role.rbac.authorization.k8s.io/csi-wekafsplugin-role created
17 rolebinding.rbac.authorization.k8s.io/csi-wekafsplugin-role-binding cre
18 daemonset.apps/csi-wekafsplugin created
19 12:04:54 deployment completed successfully
20 12:04:54 2 plugin pods are running:
21 csi-wekafsplugin-dvdh2 6/6 Running 0 3h1m
22 csi-wekafsplugin-xh182 6/6 Running 0 3h1m

The number of running pods should be the same as the number of Kubernetes worker nodes. This can be inspected by running:

1 $ kubectl get pods -n csi-wekafsplugin
2 NAME READY STATUS RESTARTS AGE
3 csi-wekafsplugin-dvdh2 6/6 Running 0 3h2m
4 csi-wekafsplugin-xh182 6/6 Running 0 3h2m