7.3 KiB

Raw Blame History

Knative Install on Google Kubernetes Engine

This guide walks you through the installation of the latest version of Knative using pre-built images.

You can find guides for other platforms here.

Before you begin

Knative requires a Kubernetes cluster v1.10 or newer. kubectl v1.10 is also required. This guide walks you through creating a cluster with the correct specifications for Knative on Google Cloud Platform.

This guide assumes you are using bash in a Mac or Linux environment; some commands will need to be adjusted for use in a Windows environment.

Installing the Google Cloud SDK and `kubectl`

If you already have gcloud installed with kubectl version 1.10 or newer, you can skip these steps.

Tip: To check which version of kubectl you have installed, enter:
```
kubectl version
```
Download and install the gcloud command line tool: https://cloud.google.com/sdk/install
Install the kubectl component:
```
gcloud components install kubectl
```
Authorize gcloud:
```
gcloud auth login
```

Setting environment variables

To simplify the command lines for this walkthrough, we need to define a few environment variables.

Set CLUSTER_NAME and CLUSTER_ZONE variables:

export CLUSTER_NAME=knative
export CLUSTER_ZONE=us-west1-c

The CLUSTER_NAME needs to be lowercase and unique among any other Kubernetes clusters in your GCP project. The zone can be any compute zone available on GCP. These variables are used later to create a Kubernetes cluster.

Setting up a Google Cloud Platform project

You need a GCP project to create a Google Kubernetes Engine cluster.

Create a new GCP project and set it as your gcloud default, or set an existing GCP project as your gcloud default:
- If you don't already have a GCP project created, create a new project in gcloud:
```
gcloud projects create my-knative-project --set-as-default
```
  Replace my-knative-project with the name you'd like to use for your GCP project.
  
  You also need to enable billing for your new project.
- If you already have a GCP project, make sure your project is set as your gcloud default:
```
gcloud config set project my-knative-project
```
  Tip: Enter gcloud config get-value project to view the ID of your default GCP project.

Enable the necessary APIs:

gcloud services enable \
  cloudapis.googleapis.com \
  container.googleapis.com \
  containerregistry.googleapis.com

Creating a Kubernetes cluster

To make sure the cluster is large enough to host all the Knative and Istio components, the recommended configuration for a cluster is:

Kubernetes version 1.10 or later
4 vCPU nodes (n1-standard-4)
Node autoscaling, up to 10 nodes
API scopes for cloud-platform, logging-write, monitoring-write, and pubsub (if those features will be used)

Create a Kubernetes cluster on GKE with the required specifications:

gcloud container clusters create $CLUSTER_NAME \
  --zone=$CLUSTER_ZONE \
  --cluster-version=latest \
  --machine-type=n1-standard-4 \
  --enable-autoscaling --min-nodes=1 --max-nodes=10 \
  --enable-autorepair \
  --scopes=service-control,service-management,compute-rw,storage-ro,cloud-platform,logging-write,monitoring-write,pubsub,datastore \
  --num-nodes=3

Grant cluster-admin permissions to the current user:

kubectl create clusterrolebinding cluster-admin-binding \
--clusterrole=cluster-admin \
--user=$(gcloud config get-value core/account)

Admin permissions are required to create the necessary RBAC rules for Istio.

Installing Istio

Knative depends on Istio.

Install Istio:

kubectl apply --filename https://raw.githubusercontent.com/knative/serving/v0.1.1/third_party/istio-0.8.0/istio.yaml

Label the default namespace with istio-injection=enabled:

kubectl label namespace default istio-injection=enabled

Monitor the Istio components until all of the components show a STATUS of Running or Completed:
```
kubectl get pods --namespace istio-system
```

It will take a few minutes for all the components to be up and running; you can rerun the command to see the current status.

Note: Instead of rerunning the command, you can add --watch to the above command to view the component's status updates in real time. Use CTRL + C to exit watch mode.

Installing Knative components

You can install the Knative Serving and Build components together, or Build on its own.

Installing Knative Serving and Build components

Run the kubectl apply command to install Knative and its dependencies:

kubectl apply --filename https://github.com/knative/serving/releases/download/v0.1.1/release.yaml

Monitor the Knative components until all of the components show a STATUS of Running:

kubectl get pods --namespace knative-serving
kubectl get pods --namespace knative-build

Installing Knative Build only

Run the kubectl apply command to install Knative Build and its dependencies:

kubectl apply --filename https://raw.githubusercontent.com/knative/serving/v0.1.1/third_party/config/build/release.yaml

Monitor the Knative Build components until all of the components show a STATUS of Running:
```
kubectl get pods --namespace knative-build
```

Just as with the Istio components, it will take a few seconds for the Knative components to be up and running; you can rerun the kubectl get command to see the current status.

Note: Instead of rerunning the command, you can add --watch to the above command to view the component's status updates in real time. Use CTRL + C to exit watch mode.

You are now ready to deploy an app or create a build in your new Knative cluster.

What's next

Now that your cluster has Knative installed, you're ready to deploy an app or create a build.

Depending on which Knative component you have installed, there are a few options for getting started:

You can follow the step-by-step Getting Started with Knative App Deployment guide.
You can view the available sample apps and deploy one of your choosing.
You can follow the step-by-step Creating a simple Knative Build guide.

Cleaning up

Running a cluster in Kubernetes Engine costs money, so you might want to delete the cluster when you're done if you're not using it. Deleting the cluster will also remove Knative, Istio, and any apps you've deployed.

To delete the cluster, enter the following command:

gcloud container clusters delete $CLUSTER_NAME --zone $CLUSTER_ZONE

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.

7.3 KiB Raw Blame History