Home > Storage > PowerStore > Virtualization and Cloud > Dell PowerStore: VMware vSphere with Tanzu and TKG Clusters > Deploy an application in a vSphere Pod
With the devops vSphere Namespace created, Kubernetes CLI Tools can be used to deploy a containerized application. The following example is a simple demonstration application named hello-kubernetes which deploys a LoadBalancer and three vSphere Pod replicas.
C:\>kubectl vsphere login --server=https://xxx.xxx.xxx.193 --vsphere-username administrator@vsphere.local --insecure-skip-tls-verify
Password:
Logged in successfully.
You have access to the following contexts:
xxx.xxx.xxx.193
devops
If the context you wish to use is not in this list, you may need to try logging in again later, or contact your cluster administrator.
To change context, use `kubectl config use-context <workload name>`
C:\>kubectl config use-context devops
Switched to context "devops".
C:\>kubectl apply -f C:\Users\jboche\Downloads\Kubernetes-master\Kubernetes-master\demo-applications\demo-hellokubernetes.yaml
service/hello-kubernetes created
deployment.apps/hello-kubernetes created
Recalling the vSphere with Tanzu deployment, the vk8s-vvol-silver VM Storage Policy was specified for Ephemeral Disks. Ephemeral Virtual Disks are transient storage for vSphere Pods which exist throughout the life cycle of the vSphere Pod.
Each vSphere Pod has one ephemeral disk that exists throughout the life cycle of the vSphere Pod. Since the hello-kubernetes application deployed three vSphere Pods, three sets of vVols will be created for the hello-kubernetes application. These vVols are not only visible in the vSphere UI, but they are also visible in the PowerStore Manager figure shown below. A filter is enabled to show only the Config and Data vVols for the hello-kubernetes application.
The IO Priority column is another area of interest. When the vk8s-vvol-silver VM Storage Policy was created, a QoS Priority of Medium was chosen. Looking at the figure above, it is clear that the hello-kubernetes application is tied to a medium IO Priority. If there is significant storage IO contention, the hello-kubernetes application will have priority over Low IO Priority workloads, but would yield to High Priority workloads. This is a working example of how a volume performance policy can be used as a storage tiering mechanism for Kubernetes workloads.
The last item to note is that storage has not yet been added to the devops vSphere Namespace. Storage is added to a vSphere Namespace to support persistent volumes and persistent volume claims. I know that the hello-kubernetes application does not use persistent storage so there was not a need to add storage to this vSphere Namespace yet. Adding storage will be covered in an upcoming section.