To set up SMB storage for a remote IFS Cloud 23R2 customer, we're configuring parameters in the ifscloud-values.yaml file. The SMB share was created by the customer’s IT team. We're aiming to ensure that the persistent volume (PV) and persistent volume claim (PVC) are released. How can we ensure they're in the "Bound" status?
Page 1 / 1
Hi AK Sahu,
Please share the output of the following:
kubectl get pv,pvc -A
kubectl describe pvc <pvc name> -n <ifs namespace>I suspect you’ll find a FailedBinding in the above describe output events.
Best regards -- Ben
Hi,
It seems PVC is deleted in your scenario. That’s why the status is “Released”.
Please share the output of the commands Ben mentioned above.
/Pasindu
Hi,
By examining the ages of the Persistent Volume (PV) and Persistent Volume Claim (PVC), we can hypothesize that the following scenario might have occurred.
It appears that the PVC or the entire IFS cloud namespace was deleted after the first installation. As a result of this deletion, the PV is now in a ‘Released’ state. There seems to have been a second installation. During this installation, a new PVC was created. However, this newly created PVC cannot bind to the existing PV because the PV is still in a ‘Released’ state. To resolve this issue, you will need to delete the existing PV and perform a reinstallation.
/Pasindu
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.