knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Markdown cleanup on the "Creating a K8s Cluster" doc (#195) 

1. Change - unordered list to use *
2. Change ordered lists to use lazy numbering (write 1 inline instead of
2-9)
3. Fix line lengths
4. Fix indentation on shell code sample
This commit is contained in:
Drew Inglis 2018-02-20 14:51:49 -08:00 committed by GitHub
parent 078611aca3
commit 1757a5485f
1 changed files with 87 additions and 83 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

62
creating-a-kubernetes-cluster.md
View File

@ -9,21 +9,21 @@ Two options:
To use a k8s cluster running in GKE: To use a k8s cluster running in GKE:
1. Install `gcloud` using 1. Install `gcloud` using [the instructions for your
[the instructions for your platform](https://cloud.google.com/sdk/downloads). platform](https://cloud.google.com/sdk/downloads).
2. Create a GCP project (or use an existing project if you've already created 1. Create a GCP project (or use an existing project if you've already created
one) at http://console.cloud.google.com/home/dashboard. Set the ID of the one) at http://console.cloud.google.com/home/dashboard. Set the ID of the
project in an environment variable (e.g. `PROJECT_ID`) along with the email project in an environment variable (e.g. `PROJECT_ID`) along with the email
of your GCP user (`GCP_USER`). of your GCP user (`GCP_USER`).
3. Enable the k8s API: 1. Enable the k8s API:
```shell ```shell
gcloud --project=$PROJECT_ID services enable container.googleapis.com gcloud --project=$PROJECT_ID services enable container.googleapis.com
``` ```
4. Create a k8s cluster (version 1.9 or greater): 1. Create a k8s cluster (version 1.9 or greater):
```shell ```shell
gcloud --project=$PROJECT_ID container clusters create \ gcloud --project=$PROJECT_ID container clusters create \
@ -33,28 +33,29 @@ To use a k8s cluster running in GKE:
--enable-autoscaling --min-nodes=1 --max-nodes=3 \ --enable-autoscaling --min-nodes=1 --max-nodes=3 \
elafros-demo elafros-demo
``` ```
- Version 1.9+ is required
- Change this to whichever zone you choose
- cloud-platform scope is required to access GCB
- Autoscale from 1 to 3 nodes. Adjust this for your use case
- Change this to your preferred cluster name
* Version 1.9+ is required
* Change this to whichever zone you choose
* cloud-platform scope is required to access GCB
* Autoscale from 1 to 3 nodes. Adjust this for your use case
* Change this to your preferred cluster name
You can see the list of supported cluster versions in a particular zone You can see the list of supported cluster versions in a particular zone by
by running: running:
```shell ```shell
# Get the list of valid versions in us-east1-d # Get the list of valid versions in us-east1-d
gcloud container get-server-config --zone us-east1-d gcloud container get-server-config --zone us-east1-d
``` ```
5. If you haven't installed `kubectl` yet, you can install it now with `gcloud`: 1. If you haven't installed `kubectl` yet, you can install it now with
`gcloud`:
```shell ```shell
gcloud components install kubectl gcloud components install kubectl
``` ```
6. Give your gcloud user cluster-admin privileges: 1. Give your gcloud user cluster-admin privileges:
```shell ```shell
kubectl create clusterrolebinding gcloud-admin-binding \ kubectl create clusterrolebinding gcloud-admin-binding \
@ -65,19 +66,22 @@ To use a k8s cluster running in GKE:
## Minikube ## Minikube
1. [Install and configure 1. [Install and configure
minikube](https://github.com/kubernetes/minikube#minikube) with a [VM minikube](https://github.com/kubernetes/minikube#minikube) with a [VM
driver](https://github.com/kubernetes/minikube#requirements), e.g. `kvm` on driver](https://github.com/kubernetes/minikube#requirements), e.g. `kvm` on
Linux or `xhyve` on macOS. Linux or `xhyve` on macOS.
2. [Create a cluster](https://github.com/kubernetes/minikube#quickstart) with version 1.9 or greater and your chosen VM driver: 1. [Create a cluster](https://github.com/kubernetes/minikube#quickstart) with
version 1.9 or greater and your chosen VM driver:
_Until minikube [enables it by default](https://github.com/kubernetes/minikube/pull/2547),the MutatingAdmissionWebhook plugin must be manually enabled._ _Until minikube [enables it by
default](https://github.com/kubernetes/minikube/pull/2547),the
MutatingAdmissionWebhook plugin must be manually enabled._
```shell ```shell
minikube start \ minikube start \
--kubernetes-version=v1.9.0 \ --kubernetes-version=v1.9.0 \
--vm-driver=kvm \ --vm-driver=kvm \
--extra-config=apiserver.Admission.PluginNames=DenyEscalatingExec,LimitRanger,NamespaceExists,NamespaceLifecycle,ResourceQuota,ServiceAccount,DefaultStorageClass,SecurityContextDeny,MutatingAdmissionWebhook --extra-config=apiserver.Admission.PluginNames=DenyEscalatingExec,LimitRanger,NamespaceExists,NamespaceLifecycle,ResourceQuota,ServiceAccount,DefaultStorageClass,SecurityContextDeny,MutatingAdmissionWebhook
``` ```
### Minikube with GCR ### Minikube with GCR
@ -101,7 +105,7 @@ You can use Google Container Registry as the registry for a Minikube cluster.
export DOCKER_REPO_OVERRIDE="${GCR_DOMAIN}/${PROJECT_ID}" export DOCKER_REPO_OVERRIDE="${GCR_DOMAIN}/${PROJECT_ID}"
``` ```
2. Create a GCP service account: 1. Create a GCP service account:
```shell ```shell
gcloud iam service-accounts create minikube-gcr \ gcloud iam service-accounts create minikube-gcr \
@ -109,7 +113,7 @@ You can use Google Container Registry as the registry for a Minikube cluster.
--project $PROJECT_ID --project $PROJECT_ID
``` ```
3. Give your service account the `storage.objectViewer` role: 1. Give your service account the `storage.objectViewer` role:
```shell ```shell
gcloud projects add-iam-policy-binding $PROJECT_ID \ gcloud projects add-iam-policy-binding $PROJECT_ID \
@ -117,7 +121,7 @@ You can use Google Container Registry as the registry for a Minikube cluster.
--role roles/storage.objectViewer --role roles/storage.objectViewer
``` ```
4. Create a key credential file for the service account: 1. Create a key credential file for the service account:
```shell ```shell
gcloud iam service-accounts keys create \ gcloud iam service-accounts keys create \
@ -129,9 +133,9 @@ Now you can use the `minikube-gcr-key.json` file to create image pull secrets
and link them to Kubernetes service accounts. _A secret must be created and and link them to Kubernetes service accounts. _A secret must be created and
linked to a service account in each namespace that will pull images from GCR._ linked to a service account in each namespace that will pull images from GCR._
For example, use these steps to allow Minikube to pull Elafros and Build For example, use these steps to allow Minikube to pull Elafros and Build images
images from GCR as built by Bazel (`bazel run :everything.create`). _This is from GCR as built by Bazel (`bazel run :everything.create`). _This is only
only necessary if you are not using public Elafros and Build images._ necessary if you are not using public Elafros and Build images._
1. Create a Kubernetes secret in the `ela-system` and `build-system` namespace: 1. Create a Kubernetes secret in the `ela-system` and `build-system` namespace:
@ -149,7 +153,7 @@ only necessary if you are not using public Elafros and Build images._
_The secret must be created in the same namespace as the pod or service _The secret must be created in the same namespace as the pod or service
account._ account._
2. Add the secret as an imagePullSecret to the `ela-controller` and 1. Add the secret as an imagePullSecret to the `ela-controller` and
`build-controller` service accounts: `build-controller` service accounts:
```shell ```shell