---
name: containers-ts-storage-cos-csi-addon
title: Debugging the Cloud Object Storage add-on
description: '[Virtual Private Cloud] [Classic infrastructure]'
last-updated: 2026-07-27
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Debugging the Cloud Object Storage add-on
{: #ts-storage-cos-csi-addon}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}


The `ibm-object-csi-driver` add-on does not run properly.


Follow these steps to gather details about the issue.

1. Pull the cluster configuration. 
    ```sh
    ibmcloud ks cluster config -c CLUSTER_NAME_OR_ID
    ```
    {: pre}
   
1. Check the health of the add-on to ensure it is deployed properly.
    ```sh
    ibmcloud ks cluster addon ls --cluster CLUSTER_NAME_OR_ID
    ```
    {: pre}

1. Check the version of the installed add-on. It is recommended to use the latest version for better support.
    ```sh
    ibmcloud ks cluster addon ls --cluster CLUSTER_NAME_OR_ID | grep ibm-object-csi-driver
    ```
    {: pre}

1. Make sure that all CSI driver pods are in `running` state.
    ```sh
    kubectl get pods -n ibm-object-csi-operator | grep ibm-object-csi
    ```
    {: pre}
  
If any CSI driver pod is in `ImagePullBackOff` state, that means the image used for pods creation is not available in the registry or there might be permission issues. Gather the output from the previous steps and, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.
  
If any CSI driver pod is in `CrashLoopBackOff` state, you can try the following steps:

1. Describe that pod.
    ```sh
    kubectl describe pod ibm-ibm-object-csi-xxx -n ibm-object-csi-operator
    ```
    {: pre}

1. Look for the container that is continuously restarting.

1. Collect logs for more details.
    ```sh
    kubectl logs ibm-ibm-object-csi-xxx -n ibm-object-csi-operator
    ```
    {: pre}

1. Upgrade the add-on to the latest version for a possible fix.

1. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.

If you need to contact support for further help, make sure that you gather the following details for the support ticket.

* Add-on health status and add-on version mentioned above.

* PVC describe
    ```sh
    kubectl describe pvc <PVC-NAME> -n <PVC-NAMESPACE>
    ```
    {: pre}

* PV describe
    ```sh
    kubectl describe pv <pv-name>
    ```
    {: pre}

* Pod describe
    ```sh
    kubectl describe pod <POD-NAME> -n <POD-NAMESPACE> 
    ```
    {: pre}

* Logs of `controller-manager` pod
    ```sh
    kubectl logs ibm-ibm-object-csi-operator-controller-manager-xxx -n ibm-object-csi-operator 
    ```
    {: pre}

* Logs of `csi-node` pod
    ```sh
    kubectl logs ibm-object-csi-node-xxx -n ibm-object-csi-operator 
    ```
    {: pre}