k3s/cluster/addons/storage-class/vsphere/default.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: thin
  annotations:
    storageclass.beta.kubernetes.io/is-default-class: "true"
  labels:
    kubernetes.io/cluster-service: "true"
provisioner: kubernetes.io/vsphere-volume
parameters:
    diskformat: thin
[addon/storage-class] update storageclass groupversion in storage-class 2017-10-22 11:50:47 +00:00			`apiVersion: storage.k8s.io/v1`
Default storage class for vSphere Fixes: 40070 2017-02-22 00:27:14 +00:00			`kind: StorageClass`
			`metadata:`
Rename default storageclasses From UX perspective, 'default' is a bad name for the default storage class: $ kubectl get storageclass NAME TYPE default (default) kubernetes.io/aws-ebs This is sort of OK, it gets more confusing when user is not happy with the preinstalled default storage class and creates its own and makes it default: NAME TYPE default kubernetes.io/aws-ebs iops (default) kubernetes.io/aws-ebs 2017-03-16 08:14:12 +00:00			`name: thin`
Default storage class for vSphere Fixes: 40070 2017-02-22 00:27:14 +00:00			`annotations:`
			`storageclass.beta.kubernetes.io/is-default-class: "true"`
			`labels:`
			`kubernetes.io/cluster-service: "true"`
			`provisioner: kubernetes.io/vsphere-volume`
			`parameters:`
			`diskformat: thin`