Installing Istio for Knative

This guide walks you through manually installing and customizing Istio for use with Knative.

If your cloud platform offers a managed Istio installation, we recommend installing Istio that way, unless you need the ability to customize your installation. If your cloud platform offers a managed Istio installation, the install guide for your specific platform will have those instructions.

Before you begin

You need:

  • A Kubernetes cluster created.
  • istioctl (v1.5.4 or later) installed.

Installing Istio

When you install Istio, there are a few options depending on your goals. For a basic Istio installation suitable for most Knative use cases, follow the Installing Istio without sidecar injection instructions. If you’re familiar with Istio and know what kind of installation you want, read through the options and choose the installation that suits your needs.

You can easily customize your Istio installation with istioctl. The below sections cover a few useful Istio configurations and their benefits.

Choosing an Istio installation

You can install Istio with or without a service mesh:

If you want to get up and running with Knative quickly, we recommend installing Istio without automatic sidecar injection. This install is also recommended for users who don’t need the Istio service mesh, or who want to enable the service mesh by manually injecting the Istio sidecars.

Installing Istio without sidecar injection

Enter the following command to install Istio:

  1. cat << EOF > ./istio-minimal-operator.yaml
  2. apiVersion: install.istio.io/v1alpha1
  3. kind: IstioOperator
  4. spec:
  5.   values:
  6.     global:
  7.       proxy:
  8.         autoInject: disabled
  9.       useMCP: false
  10.       # The third-party-jwt is not enabled on all k8s.
  11.       # See: https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens
  12.       jwtPolicy: first-party-jwt
  14.   addonComponents:
  15.     pilot:
  16.       enabled: true
  17.     prometheus:
  18.       enabled: false
  20.   components:
  21.     ingressGateways:
  22.       - name: istio-ingressgateway
  23.         enabled: true
  24.       - name: cluster-local-gateway
  25.         enabled: true
  26.         label:
  27.           istio: cluster-local-gateway
  28.           app: cluster-local-gateway
  29.         k8s:
  30.           service:
  31.             type: ClusterIP
  32.             ports:
  33.             - port: 15020
  34.               name: status-port
  35.             - port: 80
  36.               name: http2
  37.             - port: 443
  38.               name: https
  39. EOF
  41. istioctl manifest apply -f istio-minimal-operator.yaml

Installing Istio with sidecar injection

If you want to enable the Istio service mesh, you must enable automatic sidecar injection. The Istio service mesh provides a few benefits:

  • Allows you to turn on mutual TLS, which secures service-to-service traffic within the cluster.

  • Allows you to use the Istio authorization policy, controlling the access to each Knative service based on Istio service roles.

To automatic sidecar injection, set autoInject: enabled in addition to above operator configuration.

  1.     global:
  2.       proxy:
  3.         autoInject: enabled

Using Istio mTLS feature

Since there are some networking communications between knative-serving namespace and the namespace where your services running on, you need additional preparations for mTLS enabled environment.

  • Enable sidecar container on knative-serving system namespace.
  1. kubectl label namespace knative-serving istio-injection=enabled
  • Set PeerAuthentication to PERMISSIVE on knative-serving system namespace.
  1. cat <<EOF | kubectl apply -f -
  2. apiVersion: "security.istio.io/v1beta1"
  3. kind: "PeerAuthentication"
  4. metadata:
  5.   name: "default"
  6.   namespace: "knative-serving"
  7. spec:
  8.   mtls:
  9.     mode: PERMISSIVE
  10. EOF

Verifying your Istio install

View the status of your Istio installation to make sure the install was successful. It might take a few seconds, so rerun the following command until all of the pods show a STATUS of Running or Completed:

  1. kubectl get pods --namespace istio-system

Tip: You can append the --watch flag to the kubectl get commands to view the pod status in realtime. You use CTRL + C to exit watch mode.

Configuring DNS

Knative dispatches to different services based on their hostname, so it greatly simplifies things to have DNS properly configured. For this, we must look up the external IP address that Istio received. This can be done with the following command:

  1. $ kubectl get svc -n istio-system
  2. NAME                    TYPE           CLUSTER-IP   EXTERNAL-IP    PORT(S)                                      AGE
  3. cluster-local-gateway   ClusterIP      10.0.2.216   <none>         15020/TCP,80/TCP,443/TCP                     2m14s
  4. istio-ingressgateway    LoadBalancer   10.0.2.24    34.83.80.117   15020:32206/TCP,80:30742/TCP,443:30996/TCP   2m14s
  5. istio-pilot             ClusterIP      10.0.3.27    <none>         15010/TCP,15011/TCP,8080/TCP,15014/TCP       2m14s

This external IP can be used with your DNS provider with a wildcard A record; however, for a basic functioning DNS setup (not suitable for production!) this external IP address can be used with xip.io in the config-domain ConfigMap in knative-serving. You can edit this with the following command:

  1. kubectl edit cm config-domain --namespace knative-serving

Given the external IP above, change the content to:

  1. apiVersion: v1
  2. kind: ConfigMap
  3. metadata:
  4.   name: config-domain
  5.   namespace: knative-serving
  6. data:
  7.   # xip.io is a "magic" DNS provider, which resolves all DNS lookups for:
  8.   # *.{ip}.xip.io to {ip}.
  9.   34.83.80.117.xip.io: ""

Istio resources

Clean up Istio

See the Uninstall Istio.

What’s next