Add link to KB article

abrennan89 · abrennan89 · commit 5d244c2fbe79 · 2021-09-20T13:34:40.000-05:00
diff --git a/modules/serverless-rn-1-14-0.adoc b/modules/serverless-rn-1-14-0.adoc
@@ -29,4 +29,5 @@ Only the `v1beta1` version of the APIs for `KafkaChannel` and `KafkaSource` obje
 * If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
 +
 As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
-// add KB article link when ready
++
+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].
diff --git a/modules/serverless-rn-1-15-0.adoc b/modules/serverless-rn-1-15-0.adoc
@@ -22,4 +22,5 @@ The `serving.knative.dev/visibility` label, which was previously used to create
 * If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
 +
 As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
-// add KB article link when ready
++
+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].
diff --git a/modules/serverless-rn-1-16-0.adoc b/modules/serverless-rn-1-16-0.adoc
@@ -126,4 +126,5 @@ The `3scale-kourier-control` service reconciles all previously existing Knative
 * If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
 +
 As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
-// add KB article link when ready
++
+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].
diff --git a/modules/serverless-rn-1-17-0.adoc b/modules/serverless-rn-1-17-0.adoc
@@ -46,6 +46,7 @@ Ensure that you are using the latest `kn` CLI version for your {ServerlessProduc
 * If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.
 +
 As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
-// add KB article link when ready
++
+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].
 
 * The Camel-K 1.4 release is not compatible with {ServerlessProductName} version 1.17.0. This is because Camel-K 1.4 uses APIs that were removed in Knative version 0.23.0. There is currently no workaround available for this issue. If you need to use Camel-K 1.4 with {ServerlessProductName}, do not upgrade to {ServerlessProductName} version 1.17.0.

Original file line number	Diff line number	Diff line change
@@ -29,4 +29,5 @@ Only the `v1beta1` version of the APIs for `KafkaChannel` and `KafkaSource` obje
`29`	`29`	`* If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.`
`30`	`30`	`+`
`31`	`31`	`As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.`
`32`		`-// add KB article link when ready`
	`32`	`++`
	`33`	`+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].`
Original file line number	Diff line number	Diff line change
@@ -22,4 +22,5 @@ The `serving.knative.dev/visibility` label, which was previously used to create
`22`	`22`	`* If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.`
`23`	`23`	`+`
`24`	`24`	`As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.`
`25`		`-// add KB article link when ready`
	`25`	`++`
	`26`	`+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].`
Original file line number	Diff line number	Diff line change
@@ -126,4 +126,5 @@ The `3scale-kourier-control` service reconciles all previously existing Knative
`126`	`126`	`* If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.`
`127`	`127`	`+`
`128`	`128`	`As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.`
`129`		`-// add KB article link when ready`
	`129`	`++`
	`130`	`+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].`
Original file line number	Diff line number	Diff line change
@@ -46,6 +46,7 @@ Ensure that you are using the latest `kn` CLI version for your {ServerlessProduc
`46`	`46`	`* If you create a new subscription for a Kafka channel, or a new Kafka source, there might be a delay in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reports a ready status.`
`47`	`47`	`+`
`48`	`48`	`As a result, messages that are sent during the time which the data plane is not reporting a ready status might not be delivered to the subscriber or sink.`
`49`		`-// add KB article link when ready`
	`49`	`++`
	`50`	`+For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].`
`50`	`51`
`51`	`52`	`* The Camel-K 1.4 release is not compatible with {ServerlessProductName} version 1.17.0. This is because Camel-K 1.4 uses APIs that were removed in Knative version 0.23.0. There is currently no workaround available for this issue. If you need to use Camel-K 1.4 with {ServerlessProductName}, do not upgrade to {ServerlessProductName} version 1.17.0.`