#fixitfriday website rendering for GKE install (#1115)

fixes #1109
This commit is contained in:
sebgoa 2019-03-29 18:16:54 +01:00 committed by Knative Prow Robot
parent 1dd806f699
commit 4db0a43d08
1 changed files with 12 additions and 0 deletions

View File

@ -68,9 +68,11 @@ Engine cluster.
1. Set `PROJECT` environment variable, you can replace `my-knative-project` with
the desired name of your GCP project. If you don't have one, we'll create one
in the next step.
```bash
export PROJECT=my-knative-project
```
1. If you don't have a GCP project, create and set it as your `gcloud` default:
```bash
@ -92,6 +94,7 @@ Engine cluster.
> GCP project.
1. Enable the necessary APIs:
```bash
gcloud services enable \
cloudapis.googleapis.com \
@ -111,6 +114,7 @@ components, the recommended configuration for a cluster is:
`pubsub` (if those features will be used)
1. Create a Kubernetes cluster on GKE with the required specifications:
```bash
gcloud container clusters create $CLUSTER_NAME \
--zone=$CLUSTER_ZONE \
@ -121,7 +125,9 @@ components, the recommended configuration for a cluster is:
--scopes=service-control,service-management,compute-rw,storage-ro,cloud-platform,logging-write,monitoring-write,pubsub,datastore \
--num-nodes=3
```
1. Grant cluster-admin permissions to the current user:
```bash
kubectl create clusterrolebinding cluster-admin-binding \
--clusterrole=cluster-admin \
@ -152,11 +158,14 @@ Knative depends on Istio.
about an unknown type, run the second `kubectl apply` command again.
1. Label the default namespace with `istio-injection=enabled`:
```bash
kubectl label namespace default istio-injection=enabled
```
1. Monitor the Istio components until all of the components show a `STATUS` of
`Running` or `Completed`:
```bash
kubectl get pods --namespace istio-system
```
@ -196,6 +205,7 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
completed until the upgrade process finishes.
1. Run the `kubectl apply` command to install Knative and its dependencies:
```bash
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.4.0/serving.yaml \
--filename https://github.com/knative/build/releases/download/v0.4.0/build.yaml \
@ -204,6 +214,7 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
--filename https://github.com/knative/serving/releases/download/v0.4.0/monitoring.yaml \
--filename https://raw.githubusercontent.com/knative/serving/v0.4.0/third_party/config/build/clusterrole.yaml
```
> **Note**: If your install fails on the first attempt, try rerunning the
> commands. They will likely succeed on the second attempt. For background
> info and to track the upcoming solution to this problem, see issues
@ -215,6 +226,7 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
> other.
1. Monitor the Knative components until all of the components show a `STATUS` of
`Running`:
```bash
kubectl get pods --namespace knative-serving
kubectl get pods --namespace knative-build