github.com/rohankumardubey/draft-classic@v0.16.0/docs/install-minikube.md (about) 1 # Install Guide for Minikube 2 3 Get started with Draft in three easy steps: 4 5 1. Install CLI tools for Helm, Kubectl, [Minikube][] and Draft 6 1. Boot Minikube and install Tiller 7 1. Deploy your first application 8 9 Note: This document uses a local image repository with minikube. To use Draft directly with a container registry service like https://hub.docker.com or another registry service, see the configuration steps in [Drafting in the Cloud](install-advanced.md#drafting-in-the-cloud). 10 11 ## Dependencies 12 13 In order to get started, you will need to have the following: 14 15 - the latest release of minikube 16 - the latest release of kubectl 17 - the latest release of Helm 18 - the latest release of Docker 19 - A Docker repository for storing your images 20 21 All of the dependencies (except Docker) can be installed by the following: 22 23 ```shell 24 $ brew cask install minikube 25 ``` 26 27 Docker can be installed following the appropriate path in the [Install Docker](https://docs.docker.com/install/) guide. 28 29 **NOTE for Linux**: Some distributions will require `sudo` for Docker usage. For this situation, you can either use `sudo`, or follow the instructions to [manage docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user). The choice is yours. 30 31 ## Install Draft 32 33 Afterwards, fetch [the latest release of Draft](https://github.com/Azure/draft/releases). 34 35 Installing Draft via Homebrew can be done using 36 37 ```shell 38 $ brew tap azure/draft 39 $ brew install draft 40 ``` 41 42 Canary releases of the Draft client can be found at the following links: 43 44 - [Linux amd64](https://azuredraft.blob.core.windows.net/draft/draft-canary-linux-amd64.tar.gz) 45 - [macOS amd64](https://azuredraft.blob.core.windows.net/draft/draft-canary-darwin-amd64.tar.gz) 46 - [Linux ARM](https://azuredraft.blob.core.windows.net/draft/draft-canary-linux-arm.tar.gz) 47 - [Linux x86](https://azuredraft.blob.core.windows.net/draft/draft-canary-linux-386.tar.gz) 48 - [Windows amd64](https://azuredraft.blob.core.windows.net/draft/draft-canary-windows-amd64.zip) 49 50 Unpack the Draft binary and add it to your PATH. 51 52 Now that Draft has been installed, set up Draft by running this command: 53 54 ```shell 55 $ draft init 56 ``` 57 58 It will prepare $DRAFT_HOME with a default set of packs, plugins and other directories required to get working with Draft. 59 60 ## Boot Minikube 61 62 At this point, you can boot up minikube! 63 64 ```shell 65 $ minikube start 66 ... 67 Kubectl is now configured to use the cluster. 68 ``` 69 70 Now that the cluster is up and ready, minikube automatically configures kubectl, the command line tool for Kubernetes, on your machine with the appropriate authentication and endpoint information. 71 72 ```shell 73 $ kubectl cluster-info 74 Kubernetes master is running at https://192.168.99.100:8443 75 76 To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. 77 ``` 78 79 ## Install Helm 80 81 Install Helm, the Kubernetes Package Manager, in your cluster. Helm manages the lifecycle of an application in Kubernetes, and it is also how Draft deploys an application to Kubernetes. For those who prefer to work in an enforced RBAC environment, be sure to follow the [Helm Secure Configuration](https://docs.helm.sh/using_helm/#securing-your-helm-installation) instructions. 82 83 The default installation of Helm is quite simple: 84 85 ```shell 86 $ helm init 87 ``` 88 89 Wait for Helm to come up and be in a `Ready` state. You can use `kubectl -n kube-system get deploy tiller-deploy --watch` to wait for tiller to come up (the server side of Helm). 90 91 ## Configure Docker 92 93 For Minikube environments, configure Draft to build images directly using Minikube's Docker daemon, making the build process quick and redeployments speedy. To do this, run 94 95 ```shell 96 $ eval $(minikube docker-env) 97 ``` 98 99 NOTE: You will be warned that no image registry has been set when you build and deploy your first application. Since docker builds on Minikube are immediately picked up by the Kubelet, you don't require a container registry and thus can safely disable this warning by following the instructions to do so. 100 101 ## Take Draft for a Spin 102 103 Once you've completed the above steps, you're ready to climb aboard and explore the [Getting Started Guide][Getting Started] - you'll soon be sailing! 104 105 ## Cloud Setup 106 107 For more advanced users, [Cloud installation documentation](install-cloud.md) is also provided for 108 109 - configuring for remote image registries and Cloud providers 110 - running Tiller in a Kubernetes cluster with RBAC enabled 111 - running Tiller in a namespace other than kube-system 112 113 [Getting Started]: getting-started.md 114 [minikube]: https://github.com/kubernetes/minikube