Add 1.16.0 serverless release notes

modules/serverless-rn-1-14-0.adoc

@@ -1,32 +0,0 @@
-// Module included in the following assemblies:
-//
-// * serverless/release-notes.adoc
-
-[id="serverless-rn-1-14-0_{context}"]
-
-= Release Notes for Red Hat {ServerlessProductName} 1.14.0
-
-[id="new-features-1-14-0_{context}"]
-== New features
-
-* {ServerlessProductName} now uses Knative Serving 0.20.0.
-* {ServerlessProductName} uses Knative Eventing 0.20.0.
-* {ServerlessProductName} now uses Kourier 0.20.0.
-* {ServerlessProductName} now uses Knative `kn` CLI 0.20.0.
-* {ServerlessProductName} now uses Knative Kafka 0.20.0.
-* Knative Kafka on {ServerlessProductName} is now Generally Available (GA).
-+
-[IMPORTANT]
-====
-Only the `v1beta1` version of the APIs for `KafkaChannel` and `KafkaSource` objects on {ServerlessProductName} are supported. Do not use the `v1alpha1` version of these APIs, as this version is now deprecated.
-====
-* The Operator channel for installing and upgrading {ServerlessProductName} has been updated to `stable` for {product-title} 4.6 and newer versions.
-* {ServerlessProductName} is now supported on IBM Power Systems, IBM Z, and LinuxONE, except for the following features, which are not yet supported:
-** Knative Kafka functionality.
-** {ServerlessProductName} Functions developer preview.
-// Not including Camel-K since we don't document or support that yet for serverless anyway.
-
-[id="known-issues-1-14-0_{context}"]
-== Known issues
-
-* Subscriptions for the Kafka channel sometimes fail to become marked as `READY` and remain in the `SubscriptionNotMarkedReadyByChannel` state. You can fix this by restarting the dispatcher for the Kafka channel.

modules/serverless-rn-1-15-0.adoc

@@ -1,21 +0,0 @@
-// Module included in the following assemblies:
-//
-// * serverless/release-notes.adoc
-
-[id="serverless-rn-1-15-0_{context}"]
-= Release Notes for Red Hat {ServerlessProductName} 1.15.0
-
-[id="new-features-1.15.0_{context}"]
-== New features
-
-* {ServerlessProductName} now uses Knative Serving 0.21.0.
-* {ServerlessProductName} now uses Knative Eventing 0.21.0.
-* {ServerlessProductName} now uses Kourier 0.21.0.
-* {ServerlessProductName} now uses Knative `kn` CLI 0.21.0.
-* {ServerlessProductName} now uses Knative Kafka 0.21.1.
-* {FunctionsProductName} is now available as a Technology Preview.
-
-[IMPORTANT]
-====
-The `serving.knative.dev/visibility` label, which was previously used to create private services, is now deprecated. You must update existing services to use the `networking.knative.dev/visibility` label instead.
-====

modules/serverless-rn-1-16-0.adoc

@@ -0,0 +1,116 @@
+[id="serverless-rn-1-16-0_{context}"]
+= Release Notes for Red Hat {ServerlessProductName} 1.16.0
+
+[id="new-features-1-16-0_{context}"]
+== New features
+
+* {ServerlessProductName} now uses Knative Serving 0.22.0.
+* {ServerlessProductName} now uses Knative Eventing 0.22.0.
+* {ServerlessProductName} now uses Kourier 0.22.0.
+* {ServerlessProductName} now uses Knative `kn` CLI 0.22.0.
+* {ServerlessProductName} now uses Knative Kafka 0.22.0.
+* The `kn func` CLI plug-in now uses `func` 0.16.0.
+* The `kn func emit` command has been added to the functions `kn` plug-in. You can use this command to send events to test locally deployed functions.
+
+[id="fixed-issues-1-16-0_{context}"]
+== Fixed issues
+
+[id="known-issues-1-16-0_{context}"]
+== Known issues
+
+// Add a note about the following to the mTLS docs when they're ready to merge
+* If Service Mesh is enabled with mTLS, metrics for Knative Serving are disabled by default because Service Mesh prevents Prometheus from scraping metrics.
++
+If you want to enable Knative Serving metrics for use with Service Mesh and mTLS, you must complete the following steps:
+
+.. Specify `prometheus` as the `metrics.backend-destination` in the `observability` spec of the Knative Serving custom resource (CR):
++
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1alpha1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+spec:
+  config:
+    observability:
+      metrics.backend-destination: "prometheus"
+----
++
+This step prevents metrics from being disabled by default.
+
+.. Apply the following network policy to allow traffic from the Prometheus namespace:
++
+[source,yaml]
+----
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: allow-from-openshift-monitoring-ns
+  namespace: knative-serving
+spec:
+  ingress:
+  - from:
+    - namespaceSelector:
+        matchLabels:
+          name: "openshift-monitoring"
+  podSelector: {}
+  policyTypes:
+  - Ingress
+----
+
+.. Modify and reapply the default Service Mesh control plane in the `istio-system` namespace, so that it includes the following spec:
++
+[source,yaml]
+----
+spec:
+  proxy:
+    networking:
+      trafficControl:
+        inbound:
+          excludedPorts:
+          - 8444
+----
+
+* If you deploy Service Mesh CRs with the Istio ingress enabled, you might see the following warning in the `istio-ingressgateway` pod:
++
+[source,terminal]
+----
+2021-05-02T12:56:17.700398Z warning envoy config [external/envoy/source/common/config/grpc_subscription_impl.cc:101] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener(s) 0.0.0.0_8081: duplicate listener 0.0.0.0_8081 found
+----
++
+Your Knative services might also not be accessible.
++
+You can use the following workaround to fix this issue by recreating the `knative-local-gateway` service:
+
+.. Delete the existing `knative-local-gateway` service in the `istio-system` namespace:
++
+[source,terminal]
+----
+$ oc delete services -n istio-system knative-local-gateway
+----
+
+.. Create and apply a `knative-local-gateway` service that contains the following YAML:
++
+[source,yaml]
+----
+apiVersion: v1
+kind: Service
+metadata:
+ name: knative-local-gateway
+ namespace: istio-system
+ labels:
+   experimental.istio.io/disable-gateway-port-translation: "true"
+spec:
+ type: ClusterIP
+ selector:
+   istio: ingressgateway
+ ports:
+   - name: http2
+     port: 80
+     targetPort: 8081
+----
+
+* If you have 1000 Knative services on a cluster, and then perform a reinstall or upgrade of Knative Serving, there is a delay when you create the first new service after the `KnativeServing` custom resource definition (CRD) becomes `Ready`.
++
+The `3scale-kourier-control` service reconciles all previously existing Knative services before processing the creation of a new service, which causes the new service to spend approximately 800 seconds in an `IngressNotConfigured` or `Unknown` state before the state updates to `Ready`.

modules/serverless-rn-template-module.adoc

@@ -1,12 +1,7 @@
-// Module included in the following assemblies:
-//
-// * serverless/release-notes.adoc
-
 [id="serverless-rn-<version>_{context}"]
-//update the <version> to match the filename
-
 = Release Notes for Red Hat {ServerlessProductName} <VERSION>
 // add a version, e.g. Technology Preview 1.0.0
+//update the <version> to match the filename
 
 [id="new-features-<VERSION>_{context}"]
 == New features

serverless/cli_tools/kn-serving-ref.adoc

@@ -18,11 +18,10 @@ include::modules/kn-service-update.adoc[leveloffset=+2]
 include::modules/kn-service-apply.adoc[leveloffset=+2]
 include::modules/kn-service-describe.adoc[leveloffset=+2]
 
-// Uncomment at 1.16.0 release
-// [id="kn-serving-ref-domain-mapping"]
-// == kn domain commands
+[id="kn-serving-ref-domain-mapping"]
+== kn domain commands
 
-// You can use the following commands to create and manage domain mappings.
+You can use the following commands to create and manage domain mappings.
 
-// include::modules/serverless-create-domain-mapping-kn.adoc[leveloffset=+2]
-// include::modules/serverless-manage-domain-mapping-kn.adoc[leveloffset=+2]
+include::modules/serverless-create-domain-mapping-kn.adoc[leveloffset=+2]
+include::modules/serverless-manage-domain-mapping-kn.adoc[leveloffset=+2]

serverless/knative_serving/serverless-custom-domains.adoc

@@ -25,6 +25,7 @@ You can use `DomainMapping` resources to map custom domains either with or witho
 ====
 
 include::modules/serverless-create-domain-mapping.adoc[leveloffset=+1]
+include::modules/serverless-create-domain-mapping-kn.adoc[leveloffset=+1]
 
 [id="serverless-custom-domains-private-services"]
 == Configuring custom domains for private Knative services

serverless/serverless-release-notes.adoc

@@ -8,17 +8,12 @@ toc::[]
 
 For an overview of {ServerlessProductName} functionality, see xref:../serverless/serverless-getting-started.adoc#serverless-getting-started[Getting started with OpenShift Serverless].
 
-// Modules included, most to least recent
-include::modules/serverless-rn-1-15-0.adoc[leveloffset=+1]
-include::modules/serverless-rn-1-14-0.adoc[leveloffset=+1]
-
-[id="additional-resources_serverless-release-notes"]
-== Additional resources
-
+[NOTE]
+====
 {ServerlessProductName} is based on the open source Knative project.
 
-* For details about the latest Knative Serving release, see the link:https://github.com/knative/serving/releases[Knative Serving releases page].
-* For details about the latest Knative Serving Operator release, see the link:https://github.com/knative/serving-operator/releases[Knative Serving Operator releases page].
-* For details about the latest Knative CLI release, see the link:https://github.com/knative/client/releases[Knative CLI releases page].
-* For details about the latest Knative Eventing release, see the link:https://github.com/knative/eventing/releases[Knative Eventing releases page].
-* link:https://openshift-knative.github.io/docs/docs/functions/about-functions.html[{ServerlessProductName} Functions Developer Preview documentation].
+For details about the latest Knative component releases, see the link:https://knative.dev/blog/releases[Knative releases blog].
+====
+
+// Modules included, most to least recent
+include::modules/serverless-rn-1-16-0.adoc[leveloffset=+1]