Merge pull request #41629 from abrennan89/020922

SRVCOM-1288 + SRVCOM-1664: Clean up attributes, prereqs, metadata

Author: abrennan89

distr_tracing/distr_tracing_config/serverless-jaeger-integration.adoc

@@ -1,3 +1,7 @@
+// Module included in the following assemblies:
+//
+// * serverless/develop/serverless-configuring-routes.adoc
+
 :_content-type: PROCEDURE
 [id="knative-service-cluster-local_{context}"]
 = Setting cluster availability to cluster local
@@ -15,6 +19,12 @@ Developers can label individual services in the cluster with the `networking.kna
 ====
 For {ServerlessProductName} 1.15.0 and newer versions, the `serving.knative.dev/visibility` label is no longer available. You must update existing services to use the `networking.knative.dev/visibility` label instead.
 ====
+// remove note for 4.10, OSD
+
+.Prerequisites
+
+* The {ServerlessOperatorName} and Knative Serving are installed on the cluster.
+* You have created a Knative service.
 
 .Procedure
 

jaeger/jaeger_config/serverless-jaeger-integration.adoc

@@ -3,7 +3,7 @@
 // * serverless/develop/serverless-autoscaling-developer.adoc
 
 :_content-type: REFERENCE
-[id="serverless-autoscaling-developer-maxscale_context"]
+[id="serverless-autoscaling-developer-maxscale_{context}"]
 = Maximum scale bounds
 
 The maximum number of replicas that can serve an application is determined by the `maxScale` annotation. If the `maxScale` annotation is not set, there is no upper limit for the number of replicas created.

modules/knative-service-cluster-local.adoc

@@ -1,3 +1,7 @@
+// Module included in the following assemblies:
+//
+// * serverless/develop/serverless-event-sinks.adoc
+
 :_content-type: PROCEDURE
 [id="serverless-connect-sink-source-odc_{context}"]
 = Connect an event source to a sink using the Developer perspective

modules/serverless-autoscaling-developer-maxscale.adoc

@@ -1,3 +1,8 @@
+// Module included in the following assemblies:
+//
+// * serverless/develop/serverless-event-sinks.adoc
+
+:_content-type: REFERENCE
 [id="serverless-connect-trigger-sink_{context}"]
 = Connecting a trigger to a sink
 

modules/serverless-connect-sink-source-odc.adoc

@@ -1,3 +1,7 @@
+// Module included in the following assemblies:
+//
+// * serverless/develop/serverless-configuring-routes.adoc
+
 :_content-type: PROCEDURE
 [id="serverless-customize-labels-annotations-routes_{context}"]
 = Customizing labels and annotations for {product-title} routes

modules/serverless-connect-trigger-sink.adoc

@@ -2,6 +2,7 @@
 //
 // serverless/develop/serverless-event-delivery.adoc
 
+:_content-type: CONCEPT
 [id="serverless-event-delivery-component-behaviors_{context}"]
 = Event delivery behavior for Knative Eventing channels
 

modules/serverless-customize-labels-annotations-routes.adoc

@@ -0,0 +1,17 @@
+// Module included in the following assemblies:
+//
+// serverless/develop/serverless-event-delivery.adoc
+
+:_content-type: CONCEPT
+[id="serverless-event-delivery-parameters_{context}"]
+= Configurable event delivery parameters
+
+The following parameters can be configured for event delivery.
+
+Dead letter sink:: You can configure the `deadLetterSink` delivery parameter so that if an event fails to be delivered it is sent to the specified event sink.
+
+Retries:: You can set a minimum number of times that the delivery must be retried before the event is sent to the dead letter sink, by configuring the `retry` delivery parameter with an integer value.
+
+Back off delay:: You can set the `backoffDelay` delivery parameter to specify the time delay before an event delivery retry is attempted after a failure. The duration of the `backoffDelay` parameter is specified using the https://en.wikipedia.org/wiki/ISO_8601#Durations[ISO 8601] format.
+
+Back off policy:: The `backoffPolicy` delivery parameter can be used to specify the retry back off policy. The policy can be specified as either `linear` or `exponential`. When using the `linear` back off policy, the back off delay is the time interval specified between retries. When using the `exponential` backoff policy, the back off delay is equal to `backoffDelay*2^<numberOfRetries>`.

modules/serverless-event-delivery-component-behaviors.adoc

@@ -1,3 +1,7 @@
+// Module included in the following assemblies:
+//
+// * serverless/develop/serverless-configuring-routes.adoc
+
 :_content-type: PROCEDURE
 [id="serverless-openshift-routes_{context}"]
 = Configuring {product-title} routes for Knative services
@@ -13,11 +17,6 @@ When you complete the following procedure, the default {product-title} route in
 
 * The {ServerlessOperatorName} and Knative Serving component must be installed on your {product-title} cluster.
 
-[NOTE]
-====
-You must modify the replaceable values in the example commands for the following procedure.
-====
-
 .Procedure
 
 . Create a Knative service that includes the `serving.knative.openshift.io/disableRoute=true` annotation: