Introduction Obviously with the new role - I’m doing a lot in the world of Kubernetes (I should hope so, otherwise I’m doing the way wrong job…). A lot of times, I’ll want to test out some thing against a simple cluster. Minikube is generally “OK” as far as generating a single node Kubernetes cluster locally - but I really like the ability work against multiple nodes for some cases (i.

The Next Generation of Deploying Kubernetes The Cluster API Kubernetes SIG aims to drastically simplify Kubernetes cluster lifecycle in a given cloud environment by providing a declarative API on top of the common functions that you would normally perform against a cluster. In the case of todays vAdmin (today being a time before Project Pacific), we look to the Cluster API for vSphere provider (known as CAPV, for short).

Joining the Cloud Native Applications Business Unit On October 1st I’ll be joining the Cloud Native Applications Business Unit as a Staff Technical Marketing Manager, focused on Kubernetes and more specifically the “Tanzu” line of products. I’ll be reporting to Boskey Savla and telling the story of how we’re creating a platform that allows customers to Build, Run, and Manage a Kubernetes grid across any environment. I’ll have the pleasure of getting to work with the folks from Heptio, Pivotal, the Project Pacific team, as well as the existing Enterprise PKS teams - but most importantly - I’ll get to bring content around consuming these technologies out to the community!

TL;DR I used Pulumi, an open-source, Infrastructure as Code (IaC) focused tool, to build the AWS-side configurations for my Homelab’s VPN into my AWS VPC. Pulumi’s takes an IaC approach by ACTUALLY treating the IaC as “general purpose” code (JavaScript/TypeScript/GO/Python) as opposed to some form of an overlay language. The Pulumi code (program) is now stored in my GitHub repo where I can clone it down, iterate on it, use it in other CI/CD processes (Like CodeStream…hint towards a future blog post).

I mentioned previously the idea of moving a number of my lab components out of the physical Homelab and into other environments. As I shift to a more consumption driven model, I don’t want to have to worry about “how” the infrastructure is built. I want to declare what I consume, and let the platform manage it as needed. In this post I want to focus on offloading my container workloads into AWS Elastic Container Service and Fargate.

Several months ago, Jon Schulman convinced me to finally give Mac a try, and I moved completely over from being a PC user. I wish I could say it had been a bad experience; but in truth - I’ve fallen totally in love with working on a Mac! For the type of work I’m doing now, it just excels! A while back, I had done a post about what my development configuration looked like on the PC - and I’ve gotten a lot of requests to do another one now that I’m running on the Mac.

Introduction VMware ClarityUI is VMware’s standard set of UI controls which our platform interfaces are built from. Prior to ClarityUI; each business unit independently designed their interfaces, which led to quite a diverse set of interfaces - and a bit of a reputation in the community which was was not a good one… The Clarity team introduced this set of Angular components for quickly bootstrapping and building next generation user interfaces and more importantly, improved user experiences.

!!Spoiler Alert!! - This is not a “I’m moving all the things to public cloud” blog post… Added 5/7/2019 I’ve had a few discussions since posting this blog around the implication that im just moving all my “stuff” to AWS. Totally not the case by any means! Spoiler alert; this blog post was never really about me powering off my homelab. It was about the evolution of what resources i’m using to further my learning.

Here we go Again, With A Deeply Personal Blog Post I’m a firm believer that we all carry around pieces of our past with us from the time they happen, until the time we leave this world. Some of those pieces weigh more than others and often times that weight is a variable concept that changes based on what’s going on around us. Often times, we might think that eventually they go away.

Building Templates Manually is Boring AF Quite a while back I did a post around leveraging HashiCorp’s Packer product to build vSphere Templates. There was a couple gaps that existed coming out of that post… I was wicked new to Packer and had much to learn The Packer post-provisioner was immature when it came to vSphere Template conversion, meaning, it couldn’t do it at the time Refresher on Packer What is Packer?