Install on Pivotal Container Service
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.
kubectl v1.10 is also
required. This guide walks you through creating a cluster with the correct
specifications for Knative on Pivotal Container Service.
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 Pivotal Container Service
To install Pivotal Container Service (PKS), follow the documentation at https://docs.pivotal.io/runtimes/pks/1-1/installing-pks.html.
Creating a Kubernetes cluster
NOTE: Knative uses Istio sidecar injection and requires privileged mode for your init containers.
To enable privileged mode and create a cluster:
- Enable privileged mode:
- Open the Pivotal Container Service tile in PCF Ops Manager.
- In the plan configuration that you want to use, enable both of the
- Enable Privileged Containers - Use with caution
- Disable DenyEscalatingExec
- Save your changes.
- In the PCF Ops Manager, review and then apply your changes.
- Create a cluster.
Access the cluster
To retrieve your cluster credentials, follow the documentation at https://docs.pivotal.io/runtimes/pks/1-1/cluster-credentials.html.
Knative depends on Istio. Istio workloads require privileged mode for Init Containers
- Install 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.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 second
kubectl apply command again.
- Label the default namespace with
bash kubectl label namespace default istio-injection=enabled
- Monitor the Istio components until all of the components show a
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
--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.
To delete the cluster, follow the documentation at https://docs.pivotal.io/runtimes/pks/1-1/delete-cluster.html.
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.