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.
Knative requires a Kubernetes cluster v1.11 or newer. kubectl
v1.10 is also
required. This guide walks you through creating a cluster with the correct
specifications for Knative on Azure Kubernetes Service (AKS).
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.
- If you already have
azure cli
version2.0.41
or later installed, you can skip to the next section and installkubectl
Install az
by following the instructions for your operating system. See the
full installation instructions
if yours isn't listed below. You will need az cli version 2.0.37 or greater.
brew install azure-cli
- Add the azure-cli repo to your sources:
echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ wheezy main" | \ sudo tee /etc/apt/sources.list.d/azure-cli.list
- Run the following commands to install the Azure CLI and its dependencies:
sudo apt-key adv --keyserver packages.microsoft.com --recv-keys 52E16F86FEE04B979B07E28DB02C46DF417A0893 sudo apt-get install apt-transport-https sudo apt-get update && sudo apt-get install azure-cli
- If you already have
kubectl
, runkubectl version
to check your client version. If you havekubectl
v1.10 installed, you can skip to the next section and create an AKS cluster
az aks install-cli
Now that we have all the tools, we need a Kubernetes cluster to install Knative.
First let's identify your Azure subscription and save it for use later.
- Run
az login
and follow the instructions in the command output to authorizeaz
to use your account - List your Azure subscriptions:
az account list -o table
To simplify the command lines for this walkthrough, we need to define a few environment variables. First determine which region you'd like to run AKS in, along with the resource group you'd like to use.
-
Set
RESOURCE_GROUP
andLOCATION
variables:export LOCATION=eastus export RESOURCE_GROUP=knative-group export CLUSTER_NAME=knative-cluster
-
Create a resource group with the az cli using the following command if you are using a new resource group.
az group create --name $RESOURCE_GROUP --location $LOCATION
Next we will create a managed Kubernetes cluster using AKS. 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
- Three or more nodes
- Standard_DS3_v2 nodes
- RBAC enabled
-
Enable AKS in your subscription, use the following command with the az cli:
bash az provider register -n Microsoft.ContainerService
You should also ensure that theMicrosoft.Compute
andMicrosoft.Network
providers are registered in your subscription. If you need to enable them:bash az provider register -n Microsoft.Compute az provider register -n Microsoft.Network
-
Create the AKS cluster!
az aks create --resource-group $RESOURCE_GROUP \ --name $CLUSTER_NAME \ --generate-ssh-keys \ --kubernetes-version 1.11.5 \ --enable-rbac \ --node-vm-size Standard_DS3_v2
-
Configure kubectl to use the new cluster.
az aks get-credentials --resource-group $RESOURCE_GROUP --name $CLUSTER_NAME --admin
-
Verify your cluster is up and running
kubectl get nodes
Note: Gloo is available as an alternative to Istio. Gloo is not currently compatible with the Knative Eventing component. Click here to install Knative with Gloo.
Knative depends on Istio.
-
Install Istio:
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.3.0/istio-crds.yaml && \ kubectl apply --filename https://github.com/knative/serving/releases/download/v0.3.0/istio.yaml
Note: the resources (CRDs) defined in the
istio-crds.yaml
file are also included in theistio.yaml
file, 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 secondkubectl apply
command again. -
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
ofRunning
orCompleted
:bash 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.
The following commands install all available Knative components. To customize your Knative installation, see Performing a Custom Knative Installation.
- Run the
kubectl apply
command to install Knative and its dependencies:kubectl apply --filename https://github.com/knative/serving/releases/download/v0.3.0/serving.yaml \ --filename https://github.com/knative/build/releases/download/v0.3.0/release.yaml \ --filename https://github.com/knative/eventing/releases/download/v0.3.0/release.yaml \ --filename https://github.com/knative/eventing-sources/releases/download/v0.3.0/release.yaml \ --filename https://github.com/knative/serving/releases/download/v0.3.0/monitoring.yaml
- Monitor the Knative components until all of the components show a
STATUS
ofRunning
: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 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:
az aks delete --resource-group $RESOURCE_GROUP --name $CLUSTER_NAME --yes --no-wait