storageclass.storage.k8s.io "standard" not found for pvc on bare metal Kubernetes cluster

3/8/2018

I've created a persistentVolumeClaim on my custom Kubernetes cluster, however it seems to be stuck in pending...

Do I need to install/configure some additional something? OR is this functionality only available on GCP / AWS?

pvc.yaml

apiVersion: v1
kind: PersistentVolumeClaim
spec:
  storageClassName: standard
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 3Gi
metadata:
  name: testingchris

describe pvc:

Name:          testingchris
Namespace:     diyclientapps
StorageClass:  standard
Status:        Pending
Volume:        
Labels:        <none>
Annotations:   kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{},"name":"testingchris","namespace":"diyclientapps"},"spec":{"accessModes"...
Finalizers:    []
Capacity:      
Access Modes:  
Events:
  Type     Reason              Age               From                         Message
  ----     ------              ----              ----                         -------
  Warning  ProvisioningFailed  8s (x3 over 36s)  persistentvolume-controller  storageclass.storage.k8s.io "standard" not found
-- Chris Stryczynski
google-cloud-platform
kubernetes

1 Answer

3/8/2018

PVC is just a Claim, a declaration of ones requirements for persistent storage.

For PVC to bind, a PV that is matching PVC requirements must show up, and that can happen in two ways : manual provisioning (adding a PV from ie. kubectl) or with Dynamic Volume Provisioning

What you experience is that your current setup did not auto provision for your PVC

-- Radek 'Goblin' Pieczonka
Source: StackOverflow