divyenpatel

vSphere 7.0u1
-------------
    client_test.go:45: client.ServiceContent.About.FullName VMware vCenter Server 7.0.1 build-17327586
    client_test.go:46: client.ServiceContent.About.ApiVersion: 7.0.1.1
    client_test.go:47: client.ServiceContent.About.Version: 7.0.1


vSphere 7.0
-------------

divyenpatel

Created a Pod using following YAML

# cat inline-deployment.yaml 
apiVersion: apps/v1
kind: Deployment
metadata:
  name: sample-inline-deployment
  labels:

divyenpatel

CreateVolume
-------------

2020-06-08T23:02:07.101807034Z {"level":"info","time":"2020-06-08T23:02:07.101475128Z","caller":"vanilla/controller.go:475","msg":"CreateVolume: called with args {Name:pvc-ccf3130a-5fdf-44bc-88af-152e12bd20b4 CapacityRange:required_bytes:2147483648  VolumeCapabilities:[mount:<fs_type:\"ext4\" > access_mode:<mode:SINGLE_NODE_WRITER > ] Parameters:map[csimigration:true datastore-migrationparam:vsanDatastore storagepolicyname:vSAN Default Storage Policy] Secrets:map[] VolumeContentSource:<nil> AccessibilityRequirements:<nil> XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}","TraceId":"8a907298-0ea9-4a73-99ac-9594663b9e8a"}
2020-06-08T23:02:07.101832911Z {"level":"info","time":"2020-06-08T23:02:07.10162329Z","caller":"common/util.go:228","msg":"vSphere CSI Driver supports StoragePolicyName, Datastore and fsType parameters supplied from legacy in-tree provisioner. All other parameters supplied in csimigrationparams will be dropped.","TraceId":"8a907298-0ea9-4a73-99ac-9594663

divyenpatel

• Created config-map for feature states.**

# cat csi-feature-states.conf 
[FeatureStates]
csi-migration= "true"

# kubectl create configmap csi-feature-states --from-file=csi-feature-states.conf  --namespace=kube-system

divyenpatel

# Minimum Kubernetes version - 1.16
# For prior releases make sure to add required --feature-gates flags
kind: Deployment
apiVersion: apps/v1
metadata:
  name: vsphere-csi-controller
  namespace: kube-system
spec:
  replicas: 1
  strategy:

divyenpatel

#Create storage class for couchbase volumes.
kubectl create -f couchbase-sc.yaml
 
#Create couchbase service.
kubectl create -f couchbase-service.yaml
 
#Check the status of Couchbase app
kubectl get services
 
#The UI and backend services are created but nothing is accessible from master UI yet as we have just created the dns resolver.

divyenpatel

We couldn’t find that file to show.

divyenpatel

Minimal set of vCenter roles/privileges required for static only persistent volume provisioning.

Note Datastore.FileManagement is only required for the role manage-k8s-volumes, if PVC is created to bind with statically provisioned PV, and reclaim policy set to delete. When PVC is deleted, associated statically provisioned PV will also be deleted.

Entities

Roles	Privileges

divyenpatel

How to use vSphere backed shared NFS volume on the Pods located on different Nodes

Create vSphere backed volume for NFS server using vsphere-volume provisioner.

$ kubectl create -f nfs-server-vsphere-volume.yaml
storageclass "nfs-server-sc" created
persistentvolumeclaim "nfs-server-pvc" created

$ kubectl get pvc

divyenpatel

We couldn’t find that file to show.