Moving On, Moving Forward to HashiCorp Let's address this one head-on. Cody going to HashiCorp? Not exactly shocking news. If I had a dollar for every time I was asked if I was going to HashiCorp in the past year and a half, I would be sitting with Tom from MySpace on his private beach. Thats an over-exaggeration obviously, but you get the point. Within HashiCorp, I'll be joining the Consul team, as a Technical Marketing Manager.
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). It's important to note that Cluster API is a huge part of Project Pacific.
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!
NOTE: The final state of the resources created in this blog post are located on my GitHub. Feel free to hijack, reuse, do something interesting! The good stuff is in index.ts in case you don't read the rest of this post :) What This Blog Post Is Not Blogging about vendor tech is always tricky. You throw a blog up, and people have a tendency to think you're telling everyone THE RIGHT way to do it.
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.