Skip to content

Commit f285ce5

Browse files
rh-maxrh-max
committed
Add Serverless 1.18.0 release notes
Add a fixed issue %s/custom resource definition (CRD)/custom resource (CR)/ Fix Knative Kafka version Add link to a Knowledgebase article Co-authored-by: Chris Suszynski <[email protected]> s/Knowledge article/Knowledgebase article/ Add a new feature
1 parent e973a71 commit f285ce5

7 files changed

+105
-6
lines changed

‎modules/interacting-serverless-apps-http2-gRPC.adoc

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,22 @@ These routes also do not support gRPC because gRPC is transported by HTTP2.
1313
If you use these protocols in your application, you must call the application using the ingress gateway directly.
1414
To do this you must find the ingress gateway's public address and the application's specific host.
1515

16+
// FIXME: Uncomment for Serverless 1.19.0
17+
// [IMPORTANT]
18+
// ====
19+
// This method needs to expose Kourier Gateway using the `LoadBalancer` service type. You can configure this by adding the following YAML to your `KnativeServing` custom resource definition (CRD):
20+
21+
// [source,yaml]
22+
// ----
23+
// ...
24+
// spec:
25+
// ingress:
26+
// kourier:
27+
// service-type: LoadBalancer
28+
// ...
29+
// ----
30+
// ====
31+
1632
.Procedure
1733

1834
. Find the application host. See the instructions in _Verifying your serverless application deployment_.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,6 @@ Only the `v1beta1` version of the APIs for `KafkaChannel` and `KafkaSource` obje
2828

2929
* 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.
3030
+
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.
31+
As a result, messages that are sent during the time when the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
3232
+
3333
For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,6 @@ The `serving.knative.dev/visibility` label, which was previously used to create
2121

2222
* 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.
2323
+
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.
24+
As a result, messages that are sent during the time when the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
2525
+
2626
For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,12 +119,12 @@ spec:
119119
targetPort: 8081
120120
----
121121

122-
* 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`.
122+
* 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 (CR) becomes `Ready`.
123123
+
124124
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`.
125125

126126
* 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.
127127
+
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.
128+
As a result, messages that are sent during the time when the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
129129
+
130130
For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].

‎modules/serverless-rn-1-17-0.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
* The `kn func` CLI plug-in now uses `func` 0.17.0.
1313
* In the upcoming {ServerlessProductName} 1.19.0 release, the URL scheme of external routes will default to HTTPS for enhanced security.
1414
+
15-
If you do not want this change to apply for your workloads, you can override the default setting before upgrading to 1.19.0, by adding the following YAML to your `KnativeServing` custom resource definition (CRD):
15+
If you do not want this change to apply for your workloads, you can override the default setting before upgrading to 1.19.0, by adding the following YAML to your `KnativeServing` custom resource (CR):
1616
+
1717
[source,yaml]
1818
----
@@ -45,8 +45,13 @@ Ensure that you are using the latest `kn` CLI version for your {ServerlessProduc
4545

4646
* 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.
4747
+
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.
48+
As a result, messages that are sent during the time when the data plane is not reporting a ready status might not be delivered to the subscriber or sink.
4949
+
5050
For more information about this issue and possible workarounds, see link:https://access.redhat.com/articles/6343981[Knowledge Article #6343981].
5151

5252
* 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.
53+
+
54+
[NOTE]
55+
====
56+
The issue has been fixed, and Camel-K version 1.4.1 is compatible with {ServerlessProductName} 1.17.0.
57+
====

‎modules/serverless-rn-1-18-0.adoc

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
[id="serverless-rn-1-18-0_{context}"]
2+
= Release Notes for Red Hat {ServerlessProductName} 1.18.0
3+
4+
[id="new-features-1-18-0_{context}"]
5+
== New features
6+
7+
* {ServerlessProductName} now uses Knative Serving 0.24.0.
8+
* {ServerlessProductName} now uses Knative Eventing 0.24.0.
9+
* {ServerlessProductName} now uses Kourier 0.24.0.
10+
* {ServerlessProductName} now uses Knative `kn` CLI 0.24.0.
11+
* {ServerlessProductName} now uses Knative Kafka 0.24.7.
12+
* The `kn func` CLI plug-in now uses `func` 0.18.0.
13+
* In the upcoming {ServerlessProductName} 1.19.0 release, the URL scheme of external routes will default to HTTPS for enhanced security.
14+
+
15+
If you do not want this change to apply for your workloads, you can override the default setting before upgrading to 1.19.0, by adding the following YAML to your `KnativeServing` custom resource (CR):
16+
+
17+
[source,yaml]
18+
----
19+
...
20+
spec:
21+
config:
22+
network:
23+
defaultExternalScheme: "http"
24+
...
25+
----
26+
+
27+
If you want the change to apply in 1.18.0 already, add the following YAML:
28+
+
29+
[source,yaml]
30+
----
31+
...
32+
spec:
33+
config:
34+
network:
35+
defaultExternalScheme: "https"
36+
...
37+
----
38+
39+
* In the upcoming {ServerlessProductName} 1.19.0 release, the default service type by which the Kourier Gateway is exposed will be `ClusterIP` and not `LoadBalancer`.
40+
+
41+
If you do not want this change to apply to your workloads, you can override the default setting before upgrading to 1.19.0, by adding the following YAML to your `KnativeServing` custom resource (CR):
42+
+
43+
[source,yaml]
44+
----
45+
...
46+
spec:
47+
ingress:
48+
kourier:
49+
service-type: LoadBalancer
50+
...
51+
----
52+
53+
* You can now use `emptyDir` volumes with {ServerlessProductName}. See the {ServerlessProductName} documentation about Knative Serving for details.
54+
55+
* Rust templates are now available when you create a function using `kn func`.
56+
57+
[id="fixed-issues-1-18-0_{context}"]
58+
== Fixed issues
59+
60+
* The prior 1.4 version of Camel-K was not compatible with {ServerlessProductName} 1.17.0. The issue in Camel-K has been fixed, and Camel-K version 1.4.1 can be used with {ServerlessProductName} 1.17.0.
61+
62+
* Previously, if you created a new subscription for a Kafka channel, or a new Kafka source, a delay was possible in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reported a ready status.
63+
+
64+
As a result, messages that were sent during the time when the data plane was not reporting a ready status, might not have been delivered to the subscriber or sink.
65+
+
66+
In {ServerlessProductName} 1.18.0, the issue is fixed and the initial messages are no longer lost. For more information about the issue, see link:https://access.redhat.com/articles/6343981[Knowledgebase Article #6343981].
67+
68+
[id="known-issues-1-18-0_{context}"]
69+
== Known issues
70+
71+
* Older versions of the Knative `kn` CLI might use older versions of the Knative Serving and Knative Eventing APIs. For example, version 0.23.2 of the `kn` CLI uses the `v1alpha1` API version.
72+
+
73+
On the other hand, newer releases of {ServerlessProductName} might no longer support older API versions. For example, {ServerlessProductName} 1.18.0 no longer supports version `v1alpha1` of the `kafkasources.sources.knative.dev` API.
74+
+
75+
Consequently, using an older version of the Knative `kn` CLI with a newer {ServerlessProductName} might produce an error because the `kn` cannot find the outdated API. For example, version 0.23.2 of the `kn` CLI does not work with {ServerlessProductName} 1.18.0.
76+
+
77+
To avoid issues, use the latest `kn` CLI version available for your {ServerlessProductName} release. For {ServerlessProductName} 1.18.0, use Knative `kn` CLI 0.24.0.

‎serverless/serverless-release-notes.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ For details about the latest Knative component releases, see the link:https://kn
1818
include::modules/serverless-api-versions.adoc[leveloffset=+1]
1919

2020
// Modules included, most to least recent
21+
include::modules/serverless-rn-1-18-0.adoc[leveloffset=+1]
2122
include::modules/serverless-rn-1-17-0.adoc[leveloffset=+1]
2223
include::modules/serverless-rn-1-16-0.adoc[leveloffset=+1]
2324
include::modules/serverless-rn-1-15-0.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)