Deploying TKG v1.2.0 (TKGm) in an internet-restricted environment using Harbor

In this post, I am going to outline the steps involved to successfully deploy a Tanzu Kubernetes Grid  (TKG) management cluster and workload clusters in an internet restricted environment. [Note: since first writing this article, we appear to have standardized on TGKm – TKG multi-cloud – for this product. This is often referred to as an air-gapped environment. Note that for part of this exercise, a virtual machine will need to be connected to the internet in order to pull down the images requires for TKG. Once these have been downloaded and pushed up to our local Harbor container image…

CNS-CSI 2.1 with vSphere 7.0U1 – What’s new?

In this post, we will look at what is in the new release of the vSphere CSI driver for Kubernetes, as well as enhancements to Cloud Native Storage (CNS)  that handles CSI request on the vSphere infrastructure. CSI improvements will be available in version 2.1 of the driver, and the CNS components will be part of vSphere 7.0U1. Both are required for the features discussed here. The main objective of this release is two-fold: (a) to add CNS-CSI features to vSphere with Kubernetes so that it has a similar specification to the CNS-CSI features that are available with vanilla Kubernetes,…

Understanding the Tanzu portfolio (and the new names for VMware modern app products)

The new Tanzu portfolio has a plethora of new (and not so new) Kubernetes products that we are all getting used to. There are also some new names that we are using for existing VMware products. I decided to dedicate some time to figuring it all, and documenting it here for future posterity as I know others are also finding the new branding a challenge. Note that I’m not including the new suite of products that were added to the Tanzu portfolio when VMware acquired Pivotal. This post is focusing purely on the Kubernetes related products. Enterprise PKS is now…

Site Recovery Manager support for vVols – Tech Preview from VMworld 2019

Regular readers will be aware that I have been spending a lot of my time on Cloud Native Storage topics these days, whether it is bubbling up how Kubernetes clusters are consuming vSphere storage through our new CNS feature in vSphere 6.7U3, or using Velero to do lots of things like backups/restores/application mobility. However something I have been passionate about for quite a number of years now is our Virtual Volumes (vVols) feature. And while it has been rather quiet over the past couple of years, I was thrilled to see us deliver a tech preview for supporting Site Recovery…

Announcing VMware Tanzu and Project Pacific

Today at VMworld 2019, VMware announced the Tanzu portfolio. Essentially, Tanzu covers a suite of up and coming products and features which will allow our customers to Build, Run and Manage modern applications on Kubernetes, on vSphere. I’m pretty sure that this will not come as a major surprise, considering some of the acquisitions and intentions that VMware has announced recently. For example, we have already had the Heptio acquisition at the end of last year, then the Bitnami acquisition in May of this year, and more recently, we’ve seen the intent to acquire both Carbon Black and Pivotal. Heptio,…

WaveFront Collector Issues: Error in scraping containers

I was very pleased last week, as I managed to get a bunch of metrics sent from my Kubernetes cluster into Wavefront by chaining proxies together. I was successfully able to see my cluster’s Kube-state Metrics and Kubernetes Collector Metrics in Wavefront. However, on closer inspection, I noticed that a number of the built-in Wavefront Kubernetes dashboards were not being populated (Kubernetes Metrics and Kubernetes Metrics by Namespace), and then I found a number of errors in the Wavefront collector logs in my deployment. This post will describe what these errors were, and how I rectified them. There were 2…

Validating Kubernetes cluster conformance with Sonobuoy

Another product added to the VMware portfolio with the acquisition of Heptio is Sonobuoy. In a nutshell, Sonobuoy will validate the state of your Kubernetes cluster by running a suite of non-destructive tests against your cluster. As part of the end-to-end (e2e) tests that are run by Sonobuoy, there is a also a subset of conformance tests run as well. These include things like best practices and interoperability tests. This will ensure that your Kubernetes cluster (whether is an upstream version or a third-party packaged version) supports all of the necessary Kubernetes APIs. You can read more about conformance here.…