You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,27 +16,32 @@ Kubernetes Dashboard project consists of two main components. They are called he
16
16
## Preparation
17
17
18
18
Make sure the following software is installed and added to the `$PATH` variable:
19
-
*Docker (1.3+)
19
+
*docker (1.3+)
20
20
* go (1.5+)
21
21
* nodejs (4.2.2+)
22
22
* npm (1.3+)
23
23
* java (7+)
24
24
* gulp (3.9+)
25
+
* bash
25
26
26
27
Clone the repository and install the dependencies:
27
28
```
28
29
$ npm install
29
30
```
30
31
32
+
## Run dashboard inside a container
33
+
34
+
It's possible to run `gulp` and all the dependencies inside a development container. To do this, just replace `gulp [some arg]` commands with `build/run-gulp-in-docker.sh [some arg]`. If you do this, the only dependency is `docker`, and required commands such as `npm install` will be run automatically.
35
+
31
36
## Run a Kubernetes Cluster
32
37
33
-
For development it is recommended to run a local Kubernetes cluster. For your convenience, a task is provided that checks out the latest stable version, and runs it inside a Docker container. Open a separate tab in your terminal and run the following command:
38
+
For development it is recommended to run a local Kubernetes cluster. For your convenience, a task is provided that runs a small Kubernetes cluster inside Docker containers. Run the following command:
34
39
35
40
```
36
41
$ gulp local-up-cluster
37
42
```
38
43
39
-
This will build and start a lightweight local cluster, consisting of a master and a single node. All processes run locally, in Docker container. The local cluster should behave like a real cluster, however, plugins like heapster are not installed. To shut it down, type the following command that kills all running Docker containers:
44
+
This will start a lightweight local cluster. All processes run locally, in Docker containers. The local cluster should behave like a real cluster, but it has some shortcomings. See issues related to https://github.com/kubernetes/kubernetes/tree/master/docs/getting-started-guides/docker.md for more details. To shut it down, you can type the following command that kills all running Docker containers:
40
45
41
46
```
42
47
$ docker kill $(docker ps -aq)
@@ -91,11 +96,9 @@ Open a browser and access the UI under `localhost:9090.` The following processes
91
96
92
97
Dashboard backend (9090) ---> Kubernetes API server (8080)
93
98
94
-
95
-
96
99
In order to package everything into a ready-to-run Docker image, use the following task:
97
100
```
98
-
$ gulp docker-image
101
+
$ gulp docker-image:canary
99
102
```
100
103
You might notice that the Docker image is very small and requires only a few MB. Only Dashboard assets are added to a scratch image. This is possible, because the `dashboard` binary has no external dependencies. Awesome!
0 commit comments