Being an “open” company does not just mean embrace open-source solutions. It’s also meant to be open and listen to our partners with VMware being one of them. Recently, we joined arms on the NSX space which is kinda exciting!
You are not wrong, this title is very much accurate. This year is going to be a very special VMworld for me as this will be the first time Microsoft will host a booth in the Solutions Expo as well as a couple of sessions.
So it’s been quite a while since I blogged, the longest “dry season” for me since starting. Why is that?! Well, I kinda flipped my life with moving to the US and becoming a program manager in Azure Compute R&D.
It is been a bit more than two years now at Microsoft. After acting as an Azure Cloud Solutions Architect it is now time to move on in my career, and boy, so many changes at once.
We’ve come a long way with understanding and leveraging acs-engine but wait, there is more to it. We can also add Windows Agents to the mix a deploy a specific Kubernetes version.
In the previous post, I showed you how easy it is to deploy a basic K8s cluster using acs-engine. That’s great and all but most deployments requires you to consider the existing Azure environment and customer requirements. In this post, we will play a bit with custom VNet and Azure managed disks.
Now that we have all tools installed and a working IDE, it’s time to deploy an actual Kubernetes cluster using acs-engine.
Time to get all pieces in place. In order to start deploying K8s cluster using acs-engine, we need to start getting all of our tools inline such as Azure CLI, IDE environment, and the actual acs-engine binaries.
© 2012-2018 I'm all vIRTUAL