Skip to content

Latest commit

 

History

History
98 lines (66 loc) · 3.88 KB

step4.md

File metadata and controls

98 lines (66 loc) · 3.88 KB
Raw

Step 4: Install and Enable Knative

Knative Overview

In this portion of the lab, you'll learn about Knative, a new open source collaboration from IBM, Google, Pivotal, Red Hat, Cisco, and others. You'll install Istio & Knative to your cluster, and then deploy the Guestbook application to it.

Knative is built on top of Istio & Kubernetes, and is a set of primitives for enabling serverless applications on Kubernetes. Knative is made up of 3 components: Serving, Build, and Eventing.

Serving supports serving your applications, managing traffic, as well as routing and autoscaling. Build supports creating a set of steps to build your application from source code to containers, on cluster. Eventing enables you to create event producers and consumers for your application.

Install `knctl` CLI

Download the appropriate binary from the releases section of the knctl project (and optionally add it to your PATH), similar to the steps you followed earlier in Step 1.

Note: if you restart your terminal, you will need to set the KUBECONFIG environment variable again.

Mac Users:

$ chmod +x ~/Downloads/knctl-darwin-amd64
$ mv ~/Downloads/knctl-darwin-amd64 /usr/local/bin/knctl

Windows Users

Copy the executable to your PATH (somewhere easily accessible) and rename it to knctl.

After installing, verify you can access it in your terminal:

$ knctl version
Client Version: 0.1.0
Succeeded

Enable Knative (and Istio)

To enable Knative, let's use the IBM Cloud Dashboard. Make sure you have the right account chosen. In the top right of the webpage, open the drop-down and choose the IBM account.

Next, navigate to the Kubernetes dashboard by pressing the hamburger button on the top-left and choosing Kubernetes. You should see your cluster in the list, click it.

Navigate to the Addons tab and install Knative (which comes with Istio):

The install process may take a minute or two. To know when it's done you can run two commands - first see if the Istio and Knative namespaces are there:

kubectl get namespace

and you should see something like:

NAME                 STATUS   AGE
default              Active   7d18h
ibm-cert-store       Active   7d18h
ibm-system           Active   7d18h
istio-system         Active   7d17h
knative-build        Active   7d17h
knative-eventing     Active   7d17h
knative-monitoring   Active   7d17h
knative-serving      Active   7d17h
knative-sources      Active   7d17h
kube-public          Active   7d18h
kube-system          Active   7d18h

Notice the istio-system namespace, and the knative-... namespaces.

Once the namespaces are there, check to see if all of the Istio and Knative pods are running correctly:

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

You could check the pods in all of the Knative namespaces, but for this workshop only "serving" and "build" are required.

Example Output:

NAME                          READY   STATUS    RESTARTS   AGE
activator-df78cb6f9-jpvs7     2/2     Running   0          38s
activator-df78cb6f9-nhzhf     2/2     Running   0          37s
activator-df78cb6f9-qjg8w     2/2     Running   0          37s
autoscaler-6fccb66768-m4f2q   2/2     Running   0          37s
controller-56cf5965f5-8pwcg   1/1     Running   0          35s
webhook-5dcbf967cd-lxzmk      1/1     Running   0          35s

If all of the pods shown are in a Running or Completed state then you should be all set. If not, wait a couple of minutes until all the pods are Running or Completed.