One of the new features in VCF Automation version 9.0.1 is a feature called vSphere Kubernetes Service Management, or VKSM for short. This gives users access to many additional capabilities, such as Data Protection, Policy Management and Add-on Management to improve the resiliency, security, and functionality of your VKS clusters. In this post, I wanted to take a look at the Data Protection capability (VKSM DP for short), as this is something I looked at quite closely in the past. To demonstrate, we will first configure a backup location, then enable Data Protection, then test a backup and restore of…
As many readers are now aware, databases provisioned from DSM via VCF Automation have the option to create a vSphere Kubernetes Service cluster to host the database. The decision to use a VKS cluster or whether to use DSM’s own Kubernetes cluster is based on the Infrastructure Policy. If the Infrastructure Policy is built on traditional vSphere resources, then DSM’s own K8s is used. If the Infrastructure Policy points to a Supervisor Namespace, then VKS is used. In this post, I wanted to provide some tips and tricks on accessing and troubleshooting the DSM database and VKS cluster backing the…
Following on from my previous post on this topic, a number of people reached out to ask about how to add read-write-many (RWX) volumes to a Pod in VKS. Again, for dynamic volumes, this is quite simple to do. But what about some static volumes which were initially created by the Volume Service. This is a summary of what I posted in my previous blog in relation to RWX volumes. “Since RWX volumes are back by vSAN File Shares in VCF 9.0, you will need to have vSAN File Service enabled and configured. You will also have to tell the…
Security is top of mind for most, if not all, of our customers these days. Many years ago, I wrote a blog post on how customers could encrypt Kubernetes Persistent Volumes with an external Key Provider. One of our customers recently reached out to me to ask if we had any plans to provide similar support with the Native Key Provider. As my focus has been in other areas recently, I reached out to our CSI engineering team for an update. I then found out that support was added in our most recent release, vSphere 8.0U3. While no changes we…
In this series of posts, we saw in part 1 how to setup Aria Automation version 8.17. This is required for Cloud Consumption Interface support. In part 2, we saw how to enable the Cloud Consumption interface (CCI) in the Supervisor of vSphere with Tanzu. However, even though CCI is now deployed as a Supervisor Service, it is not yet completely configured to work with Aria Automation. Thus, it is still not yet possible for an Aria Automation user to interact with the Supervisor in vSphere with Tanzu to create TKG clusters or VMs using the VM Service. This is…
In the part 1 blog post, we discussed how to setup Aria Automation version 8.17 so that it could be used with Cloud Consumption Interface (CCI) to provision databases using Data Services Manager. In this post, we will look at the steps to integrate Aria Automation with CCI. There is a dependency here on vSphere 8.0U2 and vSphere with Tanzu, which we will assume has already been deployed. Thus, the main task at this point is to setup and enable the CCI Service on the Supervisor Cluster of vSphere with Tanzu. (Although I haven’t done a blog post of vSphere…
As with any product that requires some configuration steps, it is possible to input some incorrect information, and not notice that an issue has occurred until you try some deployments. In this post, I want to share some of the troubleshooting steps that I have used to figure out some misconfigurations I made with Data Services Manager 2.0. Note that this process relies on the admin having some Kubernetes skills. If this is an area you wish to develop, head on over https://kube.academy where there are a number of free lessons to get you started. You may also like to…