unable to load external plugin 'PersistentVolumeClaim'

[JuanS_OCS]

Hello all,

Maybe someone knows how to resolve this. 

According to https://learn.microsoft.com/en-us/azure/aks/azure-csi-blob-storage-provision?source=recommendations&... we mounted an Azure Data Lake Gen2 Blob into a test Pod as NFS. And it works perfectly.

When tried to mount this to the Compute pods (or CAS, does not matter), we tried to translate the compute-server-add-nfs-mount.yaml into the code Microsoft indicated. However, it complains regarding PersistenVolumeClaim plugin.

Error: external plugins disabled; unable to load external plugin 'PersistentVolumeClaim'

However, I think no plugin should be required, as it is not required either for nfs. Therefore it brings me to think I am missing something important and Basic. You can find below the code of the transformer yaml file. Perhaps you can help to find out what is missing.

Thank you in advance! 

Best regards,

Juan

# This block of code is for mounting NFS persistentVolumeClaims
# to a compute session
---
apiVersion: builtin
kind: PatchTransformer
metadata:
  name: compute-server-add-adls-nfs-mount
patch: |-
  - op: add
    path: /template/spec/volumes/-
    value:
      name: voladlsnfs001
      persistentVolumeClaim:
        claimName: pvc-voladlsnfs001
  - op: add
    path: /template/spec/containers/0/volumeMounts/-
    value:
      name: voladlsnfs001
      mountPath: "/mnt/blob"
target:
  kind: PodTemplate
  version: v1
  labelSelector: sas.com/template-intent=sas-launcher
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pvc-voladlsnfs001
  namespace: sastest
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Gi
  volumeName: pv-voladlsnfs001
  storageClassName: azureblob-nfs-premium
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-voladlsnfs001
  namespace: sastest
spec:
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain  # If set as "Delete" container would be removed after pvc deletion
  storageClassName: azureblob-nfs-premium
  csi:
    driver: blob.csi.azure.com
    readOnly: false
    # make sure volumeid is unique for every identical storage blob container in the cluster
    # character `#` is reserved for internal use and cannot be used in volumehandle
    volumeHandle: voladlsnfs001
    volumeAttributes:
      resourceGroup: ZZZZZZZZ
      storageAccount: YYYYYYYY
      containerName: XXXXXXX
      protocol: nfs

[shekhar_chavan]

This looks to be standard Viya 4 order deployment, and also seems you have raised a support track for the same with track #7613735072,

The Support team should get back to you on your query/concern you raised at the earliest.

[JuanS_OCS]

Looking forward to the response and solution!

[JuanS_OCS · Accepted solution]

Hello everyone,

I have an update for this. SAS Tech Support helped us to realize that the PersistentVolume and PersistentVolumeClaim blocks cannot be used in the transformers group. Those blocks need to be applied separately, either directly with kubectl apply, or within the resources group.

Thank you! 🙂

Best regards,

Juan