The minor version of your Google Kubernetes Engine control plane (master) cluster determines the version of Knative serving installed on your cluster.
In order to upgrade Knative serving, upgrade your GKE cluster to the minor version that supports your desired version of Knative serving. For more information about upgrading your GKE cluster, see Upgrading a cluster in the GKE documentation.
You can also track the Knative serving and cluster versions in the release notes.
For known version-related issues, see the Knative serving issues page.
The following table lists the Knative serving version that each GKE minor version supports.
Determining the version of an existing cluster
To get the Knative serving version of an existing cluster, enter the following command:
kubectl get namespace knative-serving -o 'go-template={{index .metadata.labels "serving.knative.dev/release"}}'
The output is similar to:
v0.14.0-gke.5
The first part of the returned value, v0.14.0, is the
pinned Knative version for this
Knative serving build.
The second part, gke.5, is the Knative serving build number.
Knative serving versions
0.20.0-gke.6
- References the Knative 0.20 release.
0.19.0-gke.1
- References the Knative 0.19 release.
0.18.0-gke.5
- References the Knative 0.18 release.
0.18.0-gke.4
- References the Knative 0.18 release.
0.17.2-gke.3
References the Knative 0.17 release.
Fixes CVE ISTIO-SECURITY-2020-010.
0.17.2-gke.1
- References the Knative 0.17 release.
0.16.0-gke.1
- References the Knative 0.16 release.
0.15.0-gke.3
References the Knative 0.15 release.
Knative serving now supports Managed TLS GA
0.14.0-gke.11
References the Knative 0.14 release.
Fixes CVE ISTIO-SECURITY-2020-010.
0.14.0-gke.10
References the Knative 0.14 release.
Fixes CVE-2020-11080 affecting HTTP2 library used by Envoy in Istio.
Knative serving version release process
Each Knative serving release references a Knative release. A Knative serving release is available in the Rapid release channels one to three weeks after a version of Knative is released.
The following table describes the available Google Kubernetes Engine release channels and the Knative serving strategies for releasing to those channels.
| Channel | Knative serving Release Cadence | Properties |
|---|---|---|
| Rapid | Weekly | Get the latest Knative serving release as early as possible. Gain access to new Knative serving features as soon as they go GA. Your cluster is frequently updated to use the latest technology. |
| Regular (default) | 1-2 weeks after releasing in Rapid | Recommended for most users. Access Knative serving features reasonably soon after they debut, but on a more steady and predictable release cadence. Offers a good balance of feature availability and update stability. Your cluster is upgraded 2‑3 times a month. |
| Stable | 1-2 months after releasing in Regular. | Prioritizes stability over new functionality. Changes and new versions in this channel are rolled out last, after being released on the Rapid and Regular channels. This channel allows more time for validation. Your cluster is upgraded 2‑3 times a quarter. |
Knative serving cluster upgrade process
Your GKE clusters are automatically upgraded two to three days after a new version of GKE becomes available in your cluster's release channel, unless you have configured a maintenance window or exclusion. Subscribe to the Knative serving release notes and GKE release notes for announcements.