This repo has step by step walkthroughs for two different use cases of Windows containers running on Kubernetes.
- Lift & shift of an existing .Net Framework app using SQL Server
- Starting a new application using devops tooling with Draft+Helm from the start
If you're reading this from Kubecon North America 2018, click here for instructions on how to connect to your lab VM.
After connecting, there are some important steps to get your KUBECONFIG. Keep reading on that repo to make sure you don't miss anything.
If you missed the session at Kubecon but want to build a similar lab for your team, check out these folders:
- ClusterSetup - how I set up my Kubernetes v1.13 cluster
- LabVm - how I set up the Lab VMs using Azure Labs
This is an example "lift & shift" deployment that's been moved into a modern deployment workflow with no substantial changes to the app. It builds from a traditional build server with the Visual Studio 2017 command line tools, and is packaged up with Docker.
Once you're logged into the Lab VM, visit LiftAndShiftWalkthrough for the step-by-step guide.
This works well as a cross-platform demo since premade containers are on Docker Hub for Microsoft SQL Server on Linux, and the web app remains on Windows.
This was deployed once by hand using the YAML files in k8s/*
It was also used as part of a build & release pipeline using the Helm chart in charts/fabrikamfiber. There are more details linked from https://aka.ms/winkubecon
This is a step by step guide to creating a new .Net Core app using a built-in template, along with Draft to scaffold it to Kubernetes.
Once you're logged into the Lab VM, visit DraftWalkthrough for the step-by-step guide.
This is currently set up with Draft to build and run entirely in Windows containers.
Source: eShopOnWeb
Here's all the tools I used to put the labs together. Hopefully I can turn this into a blog later on how to build your own. I'm going to call it "Shadow LabOps" - you heard it here first.
AKS-Engine - Check out the Getting started guide for Windows clusters to deploy Windows Server 2019 with Kubernetes v1.13.1 on Azure.
Helm - no changes, just used the latest release
Draft - no changes, just used the latest release
New draft packs were put together and are at https://github.com/patricklang/WindowsDraftPacks
https://docs.microsoft.com/en-us/azure/lab-services/classroom-labs/classroom-labs-overview
This was used to automate rolling out the VMs. It makes it easy to deploy an existing VM, and add log in and set up apps, then publish it. Students can check a VM out and use it without needing a paid Azure subscription. The scripts I used to install everything inside the VM are in labvm/
"Windows Server 2019 Datacenter with Containers" was used in Azure VMs. "with Containers" is not the Windows product name, it's just the VM in Azure that has Docker preinstalled and the base Windows images pulled. This saves >10 minutes of deployment time. It also puts VMs behind a NAT by default which saves time allocating public IPs.
If you're looking for a way to build your own VM for local use, check out these Packer scripts https://github.com/StefanScherer/packer-windows which build something similar
This set of scripts was run inside the VM to install all needed dev tools for the class including Visual Studio 2017, VSCode, Kubectl, Helm, and Draft https://github.com/PatrickLang/KubernetesForWindowsTutorial/tree/master/LabVm