github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-28 14:07:14 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #30226 from gmarek/guide

Browse Source 
Automatic merge from submit-queue

Small update to the kubemark guide

Fix #29882

cc @wojtek-t
This commit is contained in:
Kubernetes Submit Queue 2016-08-08 07:07:31 -07:00 committed by GitHub
commit 1bd37f477f
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/devel/kubemark-guide.md
View File

@ -61,9 +61,10 @@ resources from everything else.
## Requirements ## Requirements
To run Kubemark you need a Kubernetes cluster for running all your HollowNodes To run Kubemark you need a Kubernetes cluster (called `external cluster`)
and a dedicated machine for a master. Master machine has to be directly routable for running all your HollowNodes and a dedicated machine for a master.
from HollowNodes. You also need an access to some Docker repository. Master machine has to be directly routable from HollowNodes. You also need an
access to some Docker repository.
Currently scripts are written to be easily usable by GCE, but it should be Currently scripts are written to be easily usable by GCE, but it should be
relatively straightforward to port them to different providers or bare metal. relatively straightforward to port them to different providers or bare metal.
@ -81,10 +82,11 @@ port Kubemark to different providers.
### Starting a Kubemark cluster ### Starting a Kubemark cluster
To start a Kubemark cluster on GCE you need to create an external cluster (it To start a Kubemark cluster on GCE you need to create an external kubernetes
can be GCE, GKE or any other cluster) by yourself, build a kubernetes release cluster (it can be GCE, GKE or anything else) by yourself, make sure that kubeconfig
(e.g. by running `make quick-release`) and run `test/kubemark/start-kubemark.sh` points to it by default, build a kubernetes release (e.g. by running
script. This script will create a VM for master components, Pods for HollowNodes `make quick-release`) and run `test/kubemark/start-kubemark.sh` script.
This script will create a VM for master components, Pods for HollowNodes
and do all the setup necessary to let them talk to each other. It will use the and do all the setup necessary to let them talk to each other. It will use the
configuration stored in `cluster/kubemark/config-default.sh` - you can tweak it configuration stored in `cluster/kubemark/config-default.sh` - you can tweak it
however you want, but note that some features may not be implemented yet, as however you want, but note that some features may not be implemented yet, as