Create PVCs

• Open F5® Distributed Cloud Console > select Distributed Apps box.

Note: Homepage is role based, and your homepage may look different due to your role customization. Select All workspaces drop-down menu to discover all options. Customize Settings: Administration > Personal Management > My Account > Edit work domain & skills button > Advanced box > check Work Domain boxes > Save changes button.

Figure: Homepage

• Select the Namespace drop-down where your vK8s object is created under Distributed Apps.

Note: Confirm Namespace feature is in correct namespace, drop-down selector located in upper-left corner. Not available in all services.

• Select Applications in left-menu > select Virtual K8s.

Note: If options are not showing available, select Show link in Advanced nav options visible in bottom left corner. If needed, select Hide to minimize options from Advanced nav options mode.

• Select Name link in Virtual K8s to open dashboard.

• Select PVCs.

• Select + Add Persistant Volume Claim button.

Figure: User Management

Note: In case vK8s object is not already created, the Add virtual K8s option will be available to create vK8s. See vK8s Deployment guides for more information.

• Select YAML or JSON in drop-down menu.

• Toggle Edit Mode on.

• Enter PVC configuration in text area.

This example shows a sample application configuration.

Note: You will need to change the sample image name mentioned in the template manifest to the correct image name.

Note: You will need to change the sample image name mentioned in the template manifest to the correct image name.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-sample-app          *# The name of your claim—you’ll need this later when using the claim as the pod’s volume.*
  namespace: vk8s-pvc
spec:
  accessModes:
    - ReadWriteOnce          *# You want the storage to support a single
client (performing both reads and writes)*
  resources:
    requests:
      storage: 100Mi        *# Requesting 100M of storage*
  volumeMode: Filesystem

• Select Save button.

Figure: Create PVC in the F5 Console

• Select Deployments tab.

• Select + Add Deployments to load deployment creation form.

Note: You can also edit an existing deployment by selecting the ... > Edit option against that deployment.

Enter deployment configuration referencing PVC created in Step 6.

• Select YAML or JSON in drop-down menu.

• Toggle Edit Mode on.

• Enter configuration in kind: Deployment text area.

• Select Save button to create deployment.

Figure: Create PVC in F5 Console

Note: The persistentVolumeClaim section of the deployment configuration references the PVC in the claimName field. Ensure you specify the appropriate PVC object name. For this example, the name of PVC object created in Step 6 is used.

• Open F5® Distributed Cloud Console, select Distributed Apps box.

• Select the Namespace drop-down where your vK8s object is created under Distributed Apps.

Select Applications from the configuration menu, and Virtual K8s from the options pane.

• Select Applications > Virtual K8s.

• The vK8s object is displayed in the list.

Note: In case vK8s object is not already created, the Add virtual K8s option will be available to create vK8s. See vK8s Deployment guides for more information.

• Select ... on Virtual K8s > select Kubeconfig to download file.

Note: Save file to your desktop.

• Select date in drop-down menu in Please select credential expiry date pop-up window.

• Select Download Credential button.

Note: Download is being prepared pop-up window will appear in bottom-right initiating file download.

Figure: Kubeconfig for the vK8s Object

Create a PVC configuration file on your local machine in JSON or YAML format.

This example shows a sample application configuration.

Note: You will need to change the sample image name mentioned in the template manifest to the correct image name.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-sample-app          *# The name of your claim—you’ll need this later when using the claim as the pod’s volume.*
  namespace: vk8s-pvc
spec:
  accessModes:
    - ReadWriteOnce          *# You want the storage to support a single
client (performing both reads and writes)*
  resources:
    requests:
      storage: 100Mi        *# Requesting 100M of storage*
  volumeMode: Filesystem

Create a deployment configuration file on your local machine in JSON or YAML format.

This example shows a sample application configuration.

Note: You will need to change the sample image name mentioned in the template manifest to the correct image name.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: pvc-sample-app
  namespace: vk8s-pvc
  annotations:
    ves.io/workload-flavor: medium
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pvc-sample-app
  template:
    metadata:
      labels:
        app: pvc-sample-app
    spec:
      containers:
      - image: pvc-sample
        name: pvc-sample-app
        volumeMounts:
        - name: example-data
          mountPath: /data/db
        ports:
        - containerPort: 27017
          protocol: TCP
      volumes:
      - name: example-data
        persistentVolumeClaim:
          claimName: example-pvc *# Referencing the PersistentVolumeClaim by name in the pod volume*

Create and export KUBECONFIG environment variable using kubeconfig file downloaded in Step 3.

This example uses the kubeconfig file downloaded to the Downloads folder.

export KUBECONFIG=~/Downloads/ves_vk8s-pvc_vk8s1.yaml

Create PVC and deployment objects using the configuration files created in Step 4 and Step 5 respectively.

kubectl apply -f pvc.yml
kubectl apply -f deployment.yml

Note: You will need to change the sample image name mentioned in the template manifest to the correct image name.

kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                     STORAGECLASS   REASON   AGE
pvc-584c4a18-cf6f-4f4d-8f4a-53828ff2d999   1Gi        RWO            Delete           Bound    vk8s-pvc/pvc-sample-app   standard                3m46s

kubectl describe pv
Name:            pvc-584c4a18-cf6f-4f4d-8f4a-53828ff2d999
Labels:          <none>
Annotations:     pv.kubernetes.io/bound-by-controller: yes
                 pv.kubernetes.io/provisioned-by: kubernetes.io/azure-disk
                 volumehelper.VolumeDynamicallyCreatedByKey: azure-disk-dynamic-provisioner
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    standard
Status:          Bound
Claim:           vk8s-pvc/pvc-sample-app
Reclaim Policy:  Delete
Access Modes:    RWO
VolumeMode:      Filesystem
Capacity:        1Gi
Node Affinity:   <none>
Message:
Source:
    Type:         AzureDisk (an Azure Data Disk mount on the host and bind mount to the pod)
    DiskName:     kubernetes-dynamic-pvc-584c4a18-cf6f-4f4d-8f4a-53828ff2d999
    DiskURI:      /subscriptions/f68d94a5-1db7-4954-9a79-02b5711cb0a1/resourceGroups/demo-ce/providers/Microsoft.Compute/disks/kubernetes-dynamic-pvc-584c4a18-cf6f-4f4d-8f4a-53828ff2d999
    Kind:         Managed
    FSType:
    CachingMode:  ReadOnly
    ReadOnly:     false
Events:           <none>

Access your application using pod information obtained in Step 3.

This example opens the application shell.

Note: You will need to change the sample image name mentioned in the kubectl command to the correct image name.

kubectl exec -it pvc-sample-app-bcbf9745-6nkzz pvc-sample
Defaulting container name to pvc-sample.
Use 'kubectl describe pod/pvc-sample-bcbf9745-6nkzz -n vk8s-pvc' to see all of the containers in this pod.
pvc-sample shell version v4.2.3
connecting to: pvc-sample://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=pvc-sample
Implicit session: session { "id" : UUID("c84807bb-c22b-41c6-9103-6f51f89cd3b2") }
pvc-sample server version: 4.2.3
Welcome to the pvc-sample shell.
For interactive help, type "help".
For more comprehensive documentation, see
  http://docs.pvc-sample.org/
Questions? Try the support group
  http://groups.google.com/group/pvc-sample-user
...

>

You can perform database operations to update data to the persistent storage.

This example writes JSON documents to the application.

> use mystore
switched to db mystore
> db.foo.find()
> db.foo.insert({name:'foo'})
WriteResult({ "nInserted" : 1 })
> db.foo.insert({name:'test'})
WriteResult({ "nInserted" : 1 })
>

Verify the records from the pvc-sample shell.

> db.foo.find()
{ "_id" : ObjectId("5e7761abf01f2bc511bd6b8a"), "name" : "foo" }
{ "_id" : ObjectId("5e7761b5f01f2bc511bd6b8b"), "name" : "test" }
>
> exit
bye

Delete your deployment and recreate the deployment.

kubectl delete -f deployment.yml
deployment.apps "pvc-sample" deleted


kubectl get pods
No resources found in vk8s-pvc namespace.

kubectl apply -f deployment.yml
deployment.apps/pvc-sample created

kubectl get pods
NAME                            READY   STATUS    RESTARTS   AGE
pvc-sample-bcbf9745-g6vqv   2/2     Running   0          61s

You can delete PVCs in using the kubectl delete command or from the F5 Console.

• To delete using kubectl, specify the PVC either by file or by name.

kubectl delete -f <file.yaml>
kubectl delete pvc <pvc-name>

• To delete from the F5 Console, change to the namespace where your application is deployed.

  • Select Applications from the configuration menu, and Virtual K8s from the options pane.

  • Select on the vK8s objects and select PVCs tab in the dashboard.

  • Select ... > Delete for your PVC and confirm deletion.

Note: If you delete a PVC that is in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods. Also, if an admin deletes a PV that is bound to a PVC, the PV is not removed immediately. PV removal is postponed until the PV is no longer bound to a PVC.