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…