- Draft will need a running Kubernetes cluster to deploy your app. Minikube is a great free option.
- Draft expects Helm to be installed on your Kubernetes cluster. Download
helmv2.4.x and do ahelm initfirst, as described in Installing Helm. - Draft needs to push images to a Docker registry, so you'll need to configure Draft with your Docker registry credentials. If don't already have one, you can create a Docker registry for free on either Dockerhub.com or Quay.io.
- An ingress controller installed within your Kubernetes cluster with a wildcard domain pointing to it. Review the Ingress Guide for more information about what Draft expects and how to set up an ingress controller.
Because Draft is currently experimental, there is no stable release out yet and users are expected to be using the latest build of Draft for testing. Canary releases of the Draft client can be found at the following links:
- Linux amd64
- macOS amd64
- Windows amd64 coming soon!
Unpack the Draft binary and add it to your PATH.
To install the server-side of Draft, use draft init with your ingress' basedomain and credentials to let Draft communicate with a Docker registry by using the following command:
$ draft init --set registry.url=docker.io,registry.org=changeme,registry.authtoken=changeme,basedomain=changeme
The auth token field follows the format of Docker's X-Registry-Auth header. For credential-based logins such as Docker Hub and Quay, use:
$ echo '{"username":"jdoe","password":"secret","email":"[email protected]"}' | base64
For token-based logins such as Google Container Registry and Amazon ECR, use:
$ echo '{"registrytoken":"9cbaf023786cd7"}' | base64
Once you've completed the above steps, you're ready to climb aboard and explore the Getting Started Guide - you'll soon be sailing!