Why is the File Storage for VPC add-on in Critical state

When you list add-ons or check the File Storage for VPC add-on status configmap, you see errors similar to the following.

Troubleshoot file storage add-on ConfigMap issues.

Unable to set 'bmf' as default storage class due to internal error.
event: Change default storage class request

'EnableVPCFileCSIDriver unsuccessful, Error: resource name may not be empty, DriverVersion: v2.0.13'

The addon-vpc-file-csi-driver-configmap has missing or incorrect values.

Review file-csi-driver-status configmap for errors and update any missing or incorrect values in the addon-vpc-file-csi-driver-configmap configmap.

1. Review the add-on status.

   ibmcloud ks cluster addon ls --cluster <cluster>
   

2. Review the events in the file status configmap.

   oc get cm file-csi-driver-status -n kube-system -o yaml
   

   Example output

   apiVersion: v1
   data:
     EIT_ENABLED_WORKER_NODES: ""
     PACKAGE_DEPLOYER_VERSION: ""
     SET_DEFAULT_STORAGE_CLASS: ""
     events: |
       - description: Unable to set 'bmf' as default storage class due to internal error.
         event: Change default storage class request
         timestamp: "2025-06-26 14:07:53"
       - description: 'EnableVPCFileCSIDriver unsuccessful, Error: resource name may not
           be empty, DriverVersion: v2.0.13'
         event: EnableVPCFileCSIDriver
         timestamp: "2025-06-26 14:07:53"
   

3. Get the storage operator logs.

   kubectl logs ibm-storage-operator-xxx -n kube-system
   

4. If any property is missing or invalid, edit the value in the configmap.

   kubectl edit cm addon-vpc-file-csi-driver-configmap  -n kube-system -o yaml
   

5. After 5-10 mins check the add-on status.

   ibmcloud ks cluster addon ls --cluster <cluster>
   

6. If the issue persists, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.