---
name: containers-ts-storage-object-pvc-pod-fail-secret
title: Why does PVC or pod creation fail due to not finding the Kubernetes secret?
description: PVC or pod creation fails because the Kubernetes secret for IBM Cloud Object Storage is not found or incorrectly referenced.
last-updated: 2026-05-14
---

> ## 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.

# Why does PVC or pod creation fail due to not finding the Kubernetes secret?
{: #cos_secret_access_fails}
{: support}

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

PVC or pod creation fails because the Kubernetes secret for IBM Cloud Object Storage is not found or incorrectly referenced.
{: shortdesc}

When you create your PVC or deploy a pod that mounts the PVC, the creation or deployment fails.
{: tsSymptoms}

Example error message for a PVC creation failure:

```sh
can't get credentials: can't get secret tsecret-key: secrets "secret-key" not found
```
{: screen}

Example error message for a pod creation failure:

```sh
persistentvolumeclaim "pvc-3" not found (repeated 3 times)
```
{: screen}


The Kubernetes secret that you created is not referenced correctly in your deployment YAML file or is not set to the `ibm/ibmc-s3fs` type.
{: tsCauses}

## Resolving the issue
{: #cos-secret-resolve}

This task requires the [**Writer** or **Manager** IBM Cloud IAM service access role](https://cloud.ibm.com/docs/containers?topic=containers-iam-platform-access-roles&format=markdown) for all namespaces.
{: tsResolve}

1. List the secrets in your cluster and review the secret type. The secret must show `ibm/ibmc-s3fs` as the **Type**.

    ```sh
    kubectl get secrets --all-namespaces
    ```
    {: pre}

2. If your secret does not show `ibm/ibmc-s3fs` as the **Type**, [re-create your secret](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-understand&format=markdown#create_cos_secret).

3. Check your YAML configuration file for your PVC and pod to verify that you used the correct secret name.

4. Verify that the secret exists in the same namespace as your PVC or pod.

    ```sh
    kubectl get secret <secret_name> -n <namespace>
    ```
    {: pre}

5. After correcting the secret reference, redeploy your PVC or pod and verify it mounts successfully.

    ```sh
    kubectl get pvc
    kubectl get pods
    ```
    {: pre}