Day zero with DRAFT

Key Takeaways

hi everyone in today's episode of openet Microsoft we are going to talk about AKs draft 2 which is a day Zero AKs developer experience tool hi David welcome hi David welcome how are you hi tats I'm doing fine how are you thanks for having me pretty good so tell us something about draft tool and how how does it work sure so draft was a tool originally made by the firon team and now it's been re-imagined and it is a day Zero open- Source tool and so what that means is it helps you get your app from your local computer up and running on Azure kubernetes service or any other kubernetes service nice so do you have any working demo on if you can show us how this tool works I do so let's go ahead and take a look at my terminal here so here we can see I have installed draft from Homebrew so you can do that if you're a Mac User however if you're using Windows or Linux you can use WSL and we have an install script supporting major Linux dros you will need to have the a CLI and the GitHub CLI installed in order to use draft pretty cool and once downloaded you're going to run this tool exactly so let's take a look here we just have a go program so in here we have our main.go and we set up an HTTP server we're just going to say hello from draft so to get started with it we're going to run draft create what draft does here is it uses linguist and it tries to detect what language you're using in this case it's correct we are using go however we're not using go modules so we have to let it know now we just tell it what port we were running on which was 880 and we can accept our version so now we have a choice what kind of deployment do we want to make with draft in this case we'll use plain kubernetes manifests but it does support Helm and customize so now we just have to tell it the port one more time and we can name our app we're going to the default namespace image name and tag and here we go oh that's pretty cool so you had a project which had only one file and now you are making that project uh Deployable into AKs cluster using this tool and I can see at the end of this command there's a recommendation of draft setup GH there is so the next available option is to set up oidc or open ID connect between our GitHub repo and Azure so what that's going to do is let us connect the GitHub repo to AKs so that it can deploy those images and deploy new manifests so let's go ahead and do that now we're just going to call it draft demo so this is when it's using that a CLI and GH CLI so it's setting up that connection between our GitHub repo and our AKs cluster so that it can push new manifests and it can also push new images to your ACR that's pretty cool and I can see it is doing a whole lot of heavy lifting for the user and providing that seamless experience exactly and so now we just have to tell it which AKs cluster resource we're going to put this in and which repo we want to connect I've already set up a repo and cluster both called draft demo and that's pretty much it now it's going to start setting up that connection for us making a service principle and associating those in a secretless way using oidc which means you don't have to rotate secrets and the authentication will stay secure oh wow so it kind of saves time and it kind of avoids going and finding the best practices for workflows and to even squander around and find out what deployments to be used so this tool is pretty much just One Stop Shop up for getting your uh deployment ready for the cluster all right so I think it's because we already have this before yeah yeah the cluster was already connected so we're going to have to redo that one that's okay yeah all right and so now we pick a name for our app registration now we just pick our subscription and we tell it which resource Group and the organization in repo on GitHub we want to use that's awesome and what it is doing right now is doing all the heavy lifting for the user and I can see how this could be a very seamless experience for the user and without squandering around and finding what workflow to be used and what deployment file to be used for individual projects to get project ready from what it was to deploy it in your AKs cluster absolutely all right well fortunately for us I already set this up ahead of time so it should pretty much be good to go and we can now move on to our last command so after you run oidc we can generate a workflow which it will also prompt you at the end of so the last step we can do is we can do draft generate workflow and so now that your cluster is connected with oidc you can use generate workflow which will create a GitHub action workflow that deploys your new manifests from GitHub directly to your AKs cluster so once again the workflow depends on what kind of K8 deployment you're using since we picked manifests we'll pick it again just tell it which Azure container registry you want to save your image to you can name your image and then pick which cluster you want now for this last step we're picking which branch from GitHub we want to automatically deploy which is going to set up that continuous deployment for us and there we go now if we take a look we can see that in our GitHub folder we have this fresh workflow which will deploy using our Azure GitHub actions so it will l in using that oidc setup that we did before and then it will deploy manifests using our k8's deploy action that's awesome and I can see how we started with main.go file which was the project file and now it has automatically provided whole lot of scaffolding which is needed for deployment to your AKs cluster absolutely and so now all we need to do is add commit and push our changes and now we should be ready to hop on over so I already deployed one ahead of time since it takes a minute for these images to build and deploy onto your cluster that's awesome and so in here we can take a look we can see that I have my deployment running this was triggered automatically from your GitHub repo when you push and it will be updated when you update your code in your GitHub repo automatically using those GitHub workflows which authenticate with that oidc so just to take a look we can port forward that service that draft defined for us earlier so now we can hop on over here and take a look at what's running in our cluster here we can see our pods running that got deployed from GitHub using those oidc secrets and that K deploy action now we can go go ahead and port forward the service that draft made for us and if we hit our endpoint here we go we get hello from draft that's awesome so I can see this has now the app is now deployed to your cluster and we can see the output um that's awesome do you have any resources to be shared and how people can reach out for this open source tool I do so here's the read me on the draft repo which is azure draft we have getting started information we have a way to report bugs and request features and we welcome any Community contributions and ideas thank you so much David and I look forward for the future development around this tool really appreciate it absolutely thanks for having me TS