Install on IBM Cloud Kubernetes Service (IKS)
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.11 or newer. This guide walks you through creating a cluster with the correct specifications for Knative on IBM Cloud Kubernetes Service.
This guide assumes you are using bash in a Mac or Linux environment; some commands need to be adjusted for use in a Windows environment.
Installing the IBM Cloud developer tools
If you already have
ibmcloudinstalled with the
ibmcloud csplugin, you can skip these steps.
Download and install the
ibmcloudcommand line tool: https://console.bluemix.net/docs/cli/index.html#overview
ibmcloud plugin install container-service -r Bluemix
Setting environment variables
To simplify the command lines for this walkthrough, you need to define a few environment variables.
export CLUSTER_NAME=knative export CLUSTER_REGION=us-south export CLUSTER_ZONE=dal13
CLUSTER_NAMEmust be lowercase and unique among any other Kubernetes clusters in this IBM Cloud region.
CLUSTER_REGIONcan be any region where IKS is available. You can get a list of all available regions via the IBM Cloud documentation or via
ibmcloud cs regions.
CLUSTER_ZONEcan be any zone that is available in the specified region above. You can get a list of all avaible locations from the IBM Cloud documentation or by using
ibmcloud cs zonesafter you set the region by using
ibmcloud cs region-set $CLUSTER_REGION.
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.11 or later
- 4 vCPU nodes with 16GB memory (
ibmcloudto the appropriate region:
ibmcloud cs region-set $CLUSTER_REGION
Create a Kubernetes cluster on IKS with the required specifications:
ibmcloud cs cluster-create --name=$CLUSTER_NAME \ --zone=$CLUSTER_ZONE \ --machine-type=b2c.4x16 \ --workers=3
If you’re starting in a fresh account with no public and private VLANs, they are created automatically for you. If you already have VLANs configured in your account, get them via
ibmcloud cs vlans --zone $CLUSTER_ZONEand include the public/private VLAN in the
ibmcloud cs cluster-create --name=$CLUSTER_NAME \ --zone=$CLUSTER_ZONE \ --machine-type=b2c.4x16 \ --workers=3 \ --private-vlan $PRIVATE_VLAN_ID \ --public-vlan $PUBLIC_VLAN_ID
Wait until your Kubernetes cluster is deployed:
ibmcloud cs clusters | grep $CLUSTER_NAME
It can take a while for your cluster to be deployed. Repeat the above command until the state of your cluster is “normal”.
kubectlto the cluster:
ibmcloud cs cluster-config $CLUSTER_NAME
Follow the instructions on the screen to
KUBECONFIGvalue to point to the created cluster.
Make sure all nodes are up:
kubectl get nodes
Make sure all the nodes are in
Readystate. You are now ready to install Istio into your cluster.
Knative depends on Istio.
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.5.0/istio-crds.yaml && \ kubectl apply --filename https://github.com/knative/serving/releases/download/v0.5.0/istio.yaml
Note: the resources (CRDs) defined in the
istio-crds.yamlfile are also included in the
istio.yamlfile, but they are pulled out so that the CRD definitions are created first. If you see an error when creating resources about an unknown type, run the second
kubectl applycommand again.
Label the default namespace with
kubectl label namespace default istio-injection=enabled
Monitor the Istio components until all of the components show a
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
--watchto the above command to view the component’s status updates in real time. Use CTRL+C to exit watch mode.
The following commands install all available Knative components as well as the standard set of observability plugins. To customize your Knative installation, see Performing a Custom Knative Installation.
- If you are upgrading from Knative 0.3.x: Update your domain and static IP
address to be associated with the LoadBalancer
knative-ingressgateway. Then run the following to clean up leftover resources:
kubectl delete svc knative-ingressgateway -n istio-system kubectl delete deploy knative-ingressgateway -n istio-system
If you have the Knative Eventing Sources component installed, you will also need to delete the following resource before upgrading:
kubectl delete statefulset/controller-manager -n knative-sources
While the deletion of this resource during the upgrade process will not prevent modifications to Eventing Source resources, those changes will not be completed until the upgrade process finishes.
- Run the
kubectl applycommand to install Knative and its dependencies:
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.5.0/serving.yaml \ --filename https://github.com/knative/build/releases/download/v0.5.0/build.yaml \ --filename https://github.com/knative/eventing/releases/download/v0.5.0/release.yaml \ --filename https://github.com/knative/eventing-sources/releases/download/v0.5.0/eventing-sources.yaml \ --filename https://github.com/knative/serving/releases/download/v0.5.0/monitoring.yaml \ --filename https://raw.githubusercontent.com/knative/serving/v0.5.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 #968 and #1036.
Note: For the v0.4.0 release and newer, the
clusterrole.yamlfile is required to enable the Build and Serving components to interact with each other.
- Monitor the Knative components until all of the components show a
bash kubectl get pods --namespace knative-serving kubectl get pods --namespace knative-build kubectl get pods --namespace knative-eventing kubectl get pods --namespace knative-sources kubectl get pods --namespace knative-monitoring
Now that your cluster has Knative installed, you can see what Knative has to offer.
To deploy your first app with Knative, follow the step-by-step Getting Started with Knative App Deployment guide.
To get started with Knative Eventing, pick one of the Eventing Samples to walk through.
To get started with Knative Build, read the Build README, then choose a sample to walk through.
Running a cluster in IKS costs money, so if you’re not using it, you might want to delete the cluster when you’re done. Deleting the cluster also removes Knative, Istio, and any apps you’ve deployed.
To delete the cluster, enter the following command:
ibmcloud cs cluster-rm $CLUSTER_NAME
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.