The PVC Remains In Pending State While Deploying Fission Using Helm Chart
Problem
The following error can be seen when PVC resources are described using
kubectl.
Normal FailedBinding 3m50s (x12346 over 2d3h) persistentvolume-controller no persistent volumes available for this claim and no storage class is setOnce create the PVC can not be modified for the
storageClassNameas it is immutable.
Environment
Platform9 Managed Kubernetes - All Versions
Persistent Volumes
Helm Charts
Cause
StorageClass was not defined to bind it to the desired Persistent Volume.
Resolution
A
StorageClassis required for binding the PVCs to the existing PVs.The
storageClassvalue needs to be defined in the values.yaml file in the HelmChart for Fission.
Helm Chart uses Go Templates and the
storageClassNamein pvc.yaml file is populated from the values.yaml file.
PreviousHow To Increase Docker Image Storage Pool Size
NextUnable to Access Kubernetes Dashboard After Creating PMK Cluster
Last updated
