Storage Fusion

mkdir deploy

export cluster_name=<your ARO cluster name above>

export rg_name=<your resource group name above>

azure_cnf_secret=$(oc get secret azure-cloud-provider -n kube-system -o jsonpath="{.data.cloud-config}" | base64 --decode)

azure_cnf_secret_length=$(echo -n $azure_cnf_secret | wc -c)

aadClientId="${azure_cnf_secret:13:36}"

aadClientSecret="${azure_cnf_secret:67:$azure_cnf_secret_length}"

subId=$(az account show --query id)

tenantId=$(az account show --query tenantId -o tsv)

managed_rg=$(az aro show -n $cluster_name -g $rg_name --query 'clusterProfile.resourceGroupId' -o tsv)

managed_rg_name=`echo -e $managed_rg | cut -d  "/" -f5`

echo $tenantId

echo "subscription ID :" $subId

echo "ARO RG Name" $managed_rg_name

echo "aadClientId " $aadClientId

echo "aadClientSecret" $aadClientSecret

 
IMPORTANT: Note that the “ARO RG name” is the ARO Cluster managed resource group and not your resource group.

Copy and paste the following text into a file named azure-cloud-provider.yaml. Replace the variables with the values from the echo commands above, then apply the YAML to your cluster.

-----------

kind: ConfigMap

apiVersion: v1

metadata:

  name: azure-cred-file

  namespace: kube-system

data:

             tenantId: <$tenantId>

             subscriptionId: <$subId>

             resourceGroup: <$managed_rg_name>

             useManagedIdentityExtension: ‘false’  #Note: Use single quotes around false

             aadClientId: <$aadClientId>

             aadClientSecret: <$aadClientSecret>

--------------

 oc apply -f deploy/azure-cloud-provider.yaml

• Add-scc-to-user privileged account

 oc adm policy add-scc-to-user privileged system:serviceaccount:kube-system:csi-azurefile-node-sa

     oc describe scc privileged

4. Install CSI driver.

        Now we are ready to install the CSI driver with dynamic provisioning. 

•           Install driver using the provided cURL command.

                        driver_version=master #vv0.10.0

echo "Driver version " $driver_version

curl -skSL https://raw.githubusercontent.com/kubernetes-sigs/azurefile-csi-driver/$driver_version/deploy/install-driver.sh | bash -s $driver_version --

• Verify the CSI driver installed successfully. From the OpenShift web console, you can examine the pods in the kube-system namespace to verify they are all running or you can run the following set of commands to check the pods for errors:

oc get events -n kube-system | grep -i "Error"

for pod in $(oc get pods -l app=csi-azurefile-controller -n kube-system -o custom-columns=:metadata.name)

do

    oc describe pod $pod -n kube-system | grep -i "Error"

    oc logs $pod -c csi-provisioner -n kube-system | grep -i "Error"

    oc logs $pod -c csi-attacher -n kube-system | grep -i "Error"

    oc logs $pod -c csi-snapshotter -n kube-system | grep -i "Error"

    oc logs $pod -c csi-resizer -n kube-system | grep -i "Error"

    oc logs $pod -c liveness-probe -n kube-system | grep -i "Error"

    oc logs $pod -c azurefile -n kube-system | grep -i "Error"

done

kubectl create -f https://raw.githubusercontent.com/kubernetes-sigs/azurefile-csi-driver/master/deploy/example/storageclass-azurefile-secret.yaml

When the command is successful, you can see the storage class in the OpenShift web console.