Kubernetes PVC connection issue

Question

Kubernetes PVC connection issue

masoud habibi 20

Our website all of a sudden stopped working, and we are getting the internal server error.

I have an issue with my kubernetes cluster in Azure. My database cannot connect to PVC. It's giving me the below error:

Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[data kube-api-access-g65ls dshm]: timed out waiting for the condition

Important thing to me is that current data won't be deleted. Thank you for your help.

Mounika Reddy Anumandla 6,845 Reputation points Microsoft External Staff Moderator

2024-08-21T06:44:09.6933333+00:00
Hi masoud habibi
The error message you’re seeing, indicates that Kubernetes is struggling to attach or mount the Persistent Volume Claim (PVC) to your database pod.

Please check the status of PV and PVC and ensure that the PVC is bound to the correct PV and that the PV is in a healthy state.
kubectl get pv
*kubectl get pvc*

Verify the storage class specified in your PVC is correctly configured and has sufficient storage capacity.
*kubectl get storageclass*

Use the kubectl describe pvc <pvc-name> command to get detailed information about the PVC. Look for any events or error messages that might indicate the issue.

In Azure Kubernetes Service (AKS), Persistent Volumes (PVs) are designed to have a lifecycle independent of the pods that use them. This means that even if a pod is deleted or scaled down, the data stored in the PV remains intact. This separation ensures data persistence and reliability for your applications.

For more detailed information:https://learn.microsoft.com/en-us/azure/aks/azure-csi-disk-storage-provision
Mounika Reddy Anumandla 6,845 Reputation points Microsoft External Staff Moderator

2024-08-22T07:12:08.93+00:00

Hi masoud habibi,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others.

Accepted answer

1 additional answer

Your answer

Mounika Reddy Anumandla 6,845 Reputation points Microsoft External Staff Moderator

2024-08-21T06:44:09.6933333+00:00

Hi masoud habibi
The error message you’re seeing, indicates that Kubernetes is struggling to attach or mount the Persistent Volume Claim (PVC) to your database pod.

Please check the status of PV and PVC and ensure that the PVC is bound to the correct PV and that the PV is in a healthy state.
kubectl get pv
*kubectl get pvc*

Verify the storage class specified in your PVC is correctly configured and has sufficient storage capacity.
*kubectl get storageclass*

Use the kubectl describe pvc <pvc-name> command to get detailed information about the PVC. Look for any events or error messages that might indicate the issue.

In Azure Kubernetes Service (AKS), Persistent Volumes (PVs) are designed to have a lifecycle independent of the pods that use them. This means that even if a pod is deleted or scaled down, the data stored in the PV remains intact. This separation ensures data persistence and reliability for your applications.

For more detailed information:https://learn.microsoft.com/en-us/azure/aks/azure-csi-disk-storage-provision
Mounika Reddy Anumandla 6,845 Reputation points Microsoft External Staff Moderator

2024-08-22T07:12:08.93+00:00

Hi masoud habibi,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others.

Answer 1

Mounika Reddy Anumandla 6,845 Microsoft External Staff Moderator

Hi masoud habibi

Thank you for confirming that the issue is resolved.

As an original poster cannot accept their own answer, I am reposting it so that you can accept it an answer. Accepted answer will help other community members navigate to the appropriate solutions.

Issue: Kubernetes PVC connection issue

**Solution:**The root cause turned out to be one of the nodes where the volume and the pod were running. We had to remove and make a new node.

Answer 2

masoud habibi 20

The root cause turned out to be one of the nodes where the volume and the pod were running. We had to remove and make a new node. Thank you for your help.

Mounika Reddy Anumandla 6,845 Reputation points Microsoft External Staff Moderator

2024-08-23T06:43:16.19+00:00

Hi masoud habibi,

Thank you for confirming that the issue is resolved.
As an original poster cannot accept their own answer, I am reposting it so that you can accept it as answer. Accepted answer will help other community members navigate to the appropriate solutions.

Issue: Kubernetes PVC connection issue.

Solution: The root cause turned out to be one of the nodes where the volume and the pod were running. We had to remove and make a new node.

Share via

Kubernetes PVC connection issue

1 additional answer

Your answer