the default GitOps source repository for booting up Jenkins X
修訂 | ccbf358bd458bbbd2856a2c6f41905efcf1ff9a6 (tree) |
---|---|
時間 | 2019-07-02 16:41:41 |
作者 | James Strachan <james.strachan@gmai...> |
Commiter | James Strachan |
polish the readme
@@ -7,9 +7,8 @@ This repository contains the source code for the Jenkins X Development Environme | ||
7 | 7 | |
8 | 8 | ### Creating a kubernetes cluster |
9 | 9 | |
10 | -* either use Terraform to spin up a GKE cluster with a `jx` namespace | |
11 | -* create an empty GKE clsuer by hand e.g. via `jx create cluster gke --skip-installation` | |
12 | - * then create a `jx` namespace via `kubectl create ns jx` | |
10 | +* either use Terraform to spin up a GKE cluster with a `jx` namespace and any necessary cloud resources (e.g. on GCP we need a Kaniko Service Account and Secret) | |
11 | +* create an empty GKE cluster by hand e.g. via `jx create cluster gke --skip-installation` or using the [GCP Console](https://console.cloud.google.com/) | |
13 | 12 | |
14 | 13 | ### Run the new Jenkins X Bootstrap Pipeline |
15 | 14 |
@@ -21,6 +20,8 @@ From inside the git clone of this repository type: | ||
21 | 20 | jx boot |
22 | 21 | ``` |
23 | 22 | |
23 | +If you are not in a clone of a boot git repository then `jx boot` will clone this repository and `cd` into the clone. | |
24 | + | |
24 | 25 | The bootstrap process runs the Jenkins X Pipeline in interpret mode as there's nothing running in your Kubernetes cluster yet and so there's no server side tekton controller until after we bootstrap. |
25 | 26 | |
26 | 27 | The bootstrap process will also ask you for various important `parameters` which are used to populate a bunch of `Secrets` stored in either Vault or the local file system (well away from your git clone). |