Getting Started with VCF Part 6 – Workload Domain

The VMware Cloud Foundation 3.9 journey continues. In this post, we are going to build our very first workload domain (WLD). In part 5, we commissioned 3 x vSphere 6.7U3 ESXi hosts that will form the basis of our new WLD. A number of actions will take place during this deployment. Firstly, a new 6.7 vCenter Server will be deployed in the management domain. Then, the 3 commissioned ESXi hosts will be clustered together, allowing vSAN and vSphere HA to be enabled. We will also see NSX-T (version 2.5) deployed for the WLD as I am going to deploy NSX-T…

Getting started with VCF Part 4 – vRA Deployment

After taking care of all of the prerequisite steps highlighted in my VMware Cloud Foundation Part 3 post, we are now ready to deploy vRealize Automation (vRA) via vRealize Suite Lifecycle Manager (vRSLM) in the VCF SDDC Manager. This will be a relatively shorter “show and tell” post, which will take you through the deployment steps. It will also show you how you can monitor the progress of the vRA deployment. The complete deployment does take some time since there are quite a number of virtual appliances and virtual machines that need to be rolled out for vRA (11 in…

Getting started with VMware Cloud Foundation (VCF)

After returning from the holidays, one of the items at the top of my agenda was to become more familiarity with VMware Cloud Foundation (VCF). For those of you who are not familiar with VCF, it is basically the ‘easy button’ for deploying the full vSphere stack of products, including virtual storage (vSAN), virtual networking (NSX) as well as monitoring and logging products such as vRealize Operation, vRealize Log Insight and so on. However, it is so much more, because once VCF is stood up, it becomes the building block for the deployment of what could be termed the application…

Kubernetes on vSphere 101 – Ingress

As I was researching content for the 101 series, I came across the concept of an Ingress. As I hadn’t come across it before, I wanted to do a little more research on what it actually did. It seems that in some ways, they achieve the same function as a Load Balancer in so far as they provide a mean of allowing external traffic into your cluster. But they are significantly different in how they do this. If we take the Load Balancer service type first, then for every service that is exposed via a Load Balancer, a unique external…

A first look at vRealize Network Insight for Kubernetes

Regular readers will know that I have been spending quite a bit of time recently looking at Kubernetes running on vSphere. I’ve written a number of posts on the storage side of things, which you can read here as part of my 101 series. I also posted about how you can setup vRealize Operations Manager 7.5 and add the Management Pack for Container Monitoring. This provide some really good dashboards for examining the state of your K8s clusters, as well as detailed breakdowns into K8s node VM health and performance (CPU, Memory, DIsk IO). Not only that, but you can…

Kubernetes on vSphere 101 – Services

This will be last article in the 101 series, as I think I have covered off most of the introductory storage related items at this point. One object that came up time and again during the series was services. While not specifically a storage item, it is a fundamental building block of Kubernetes applications. In the 101 series, we came across a “headless” service with the Cassandra StatefulSet demo. This was where service type ClusterIP was set to None. When we started to look at ReadWriteMany volumes, we used NFS to demonstrate these volumes in action. In the first NFS…

NSX-T Adapter for vROps – Collection Failed

Very short post – simply to highlight an issue I came across and could not find any external reference to. I added a new adapter to my vRealize Operations Manager 7.5 to monitor my NSX-T 2.3.1 deployment. The adapter was the NSX-T 2.0 Adapter. Soon after configuring it to communicate to my NSX Manager, the Collection Status for the adapter changed to Object down and the Adapter Status changes to Collection Failed. Initially I thought it as some interoperability issue, but that wasn’t the case. I went ahead and looked at the dashboard, and it reported that the Adapter Instance…