Draft: Streamlined Kubernetes Development
Draft makes it easier for developers to build applications that run on Kubernetes by doing two main things:
draft createcommand gives developers the artifacts they need to build and run their applications in Kubernetes
draft upcommand builds the container image for an application and deploys it to Kubernetes
Draft targets the "inner loop" of a developer's workflow: as they hack on code, but before code is committed to version control.
Install the draft binary
To install via homebrew, run
brew tap azure/draft && brew install draft or download the binary via the github releases page
Using Draft is as simple as:
draft initto set up draft (after prerequisites are installed)
draft createto containerize your application based on Draft packs
draft upto deploy your application to a Kubernetes dev sandbox, accessible using
draft connectover a secured tunnel.
- Use a local editor to modify the application, with changes deployed to Kubernetes in seconds.
Once the developer is happy with changes made via Draft, they commit and push to version control, after which a continuous integration (CI) system takes over. Draft builds upon Kubernetes Helm and the Kubernetes Chart format, making it easy to construct CI pipelines from Draft-enabled applications.
Use the Minikube install guide to install and use Draft locally with Minikube. The default installation skips pushing the image, deploying directly from the local repository, which makes developer work very fast.
Use the Cloud provider install guide to install and use Draft to build locally but push images to a public (or private) repository and deploy into a Kubernetes cluster offered by a cloud provider such as Azure, Google, AWS, or any other provider.
Remember, however, take note of the major changes in releases greater than 0.12 if you have already used Draft. It's different. No, really.
Take Draft for a Spin
Climb aboard and explore the Getting Started Guide - you'll soon be sailing!
NOTE: Draft is experimental and does not have a stable release yet.
If you're having issues after upgrading draft, try deleting the draft home directory where all the draft configuration files live and then re-run the
draft init command (shown below). You'll have to re-install any custom plugins and configuration after deleting
$ draft home /Users/admin/.draft $ rm -rf $(draft home) $ draft init
Starting with the 0.12 release, Draft moves the containment and deployment engine to your local machine. This changes quite a bit about how Draft works compared to prior releases; for details, see the changelog.
For previous users, this change means that you now have more control over where your container images are stored, and in the local Minikube environment you can skip pushing the images entirely, which speeds up the developer iteration speed dramatically. (Short version without jargon: you can build and run your app really fast.) However, when you want to push your images to an image registry service like Docker hub (or ACR, GCR, Quay.io, and so on) you must inform draft which registry to use and your cluster must have access to the secrets for that registry.
We're always looks for contributions in the form of issues, pull requests, and docs changes. If you see anything that would make Draft a better experience for yourself or others, please feel free to contribute. See the contributing section below for more details!
If you're looking to build from source or get started hacking on Draft, please see the hacking guide for more information.
This software is covered under the MIT license. You can read the license here.
This software contains code from Helm, which is covered by the Apache v2.0 license.
You can read third-party software licenses here.