K
Q

Kubernetes: volume.beta.kubernetes.io/storage-class or spec.StorageClassName

8/10/2018

We're requesting persistence on kubernetes using persistence volume claim.

Currently, we're setting storage class using volume.beta.kubernetes.io/storage-class annotation:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: vault-file-backend-volumeclaim
  annotations:
    volume.beta.kubernetes.io/storage-class: heketi
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

However, we've realized that exists an spec.storageClassName field, we don't know what's it for...

Could we remove volume.beta.kubernetes.io/storage-class annotation by setting spec.storageClassName?

-- Jordi
kubernetes

Similar Questions

kubectl exec vs ssh using bastion
spark on k8s - Error 'Invalid initial heap size: -Xms'
How to use service name instead of External IP/domain name for a service endpoint url in kubernetes
kubernetes CI/CD: automate docker build, tag and push tasks on a CI/CD infrastructure
How to allow an assume role connect from EC2 to EKS on AWS?
'Develop on Kubernetes stopped working since Intellij Update'

1 Answer

8/10/2018

Yes, you should opt for storageClassName, because the annotation will be deprecated in the future, as state in kubernetes.io:

In the past, the annotation volume.beta.kubernetes.io/storage-class was used instead of the storageClassName attribute. This annotation is still working, however it will become fully deprecated in a future Kubernetes release.

So your YML file will be the following:

storageclass.yml:

apiVersion: storage.k8s.io/v1beta1  
kind: StorageClass  
metadata:  
  name: heketi
provisioner: kubernetes.io/glusterfs  
parameters:  
  resturl: [...]
  restuser: [...]
  restuserkey: [...]

pv.yml:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: vault-file-backend-volumeclaim
spec:
  storageClassName: heketi
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
-- Nicola Ben
Source: StackOverflow