Skip to content

Commit 058b6f0

Browse files
abrennan89abrennan89
committed
SRVCOM-1409: Serverless 1.17.0 release notes
1 parent 1b70f6b commit 058b6f0

File tree

8 files changed

+93
-7
lines changed

8 files changed

+93
-7
lines changed

‎modules/serverless-api-versions.adoc‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
[id="serverless-api-versions_{context}"]
2+
= About API versions
3+
4+
The {ServerlessOperatorName} automatically upgrades older resources that use deprecated versions of APIs to use the latest version.
5+
6+
For example, if you have created resources on your cluster that use older versions of the `ApiServerSource` API, such as `v1beta1`, the {ServerlessOperatorName} automatically updates these resources to use the `v1` version of the API when this is available and the `v1beta1` version is deprecated.
7+
8+
After they have been deprecated, older versions of APIs might be removed in any upcoming release. Using deprecated versions of APIs does not cause resources to fail. However, if you try to use a version of an API that has been removed, it will cause resources to fail. Ensure that your manifests are updated to use the latest version to avoid issues.

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,8 @@ Only the `v1beta1` version of the APIs for `KafkaChannel` and `KafkaSource` obje
2525
== Known issues
2626

2727
* 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.
28+
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+
+
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

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

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[id="serverless-rn-1-15-0_{context}"]
22
= Release Notes for Red Hat {ServerlessProductName} 1.15.0
33

4-
[id="new-features-1.15.0_{context}"]
4+
[id="new-features-1-15-0_{context}"]
55
== New features
66

77
* {ServerlessProductName} now uses Knative Serving 0.21.0.
@@ -15,3 +15,11 @@
1515
====
1616
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.
1717
====
18+
19+
[id="known-issues-1-15-0_{context}"]
20+
== Known issues
21+
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+
+
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

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@
1515
[id="known-issues-1-16-0_{context}"]
1616
== Known issues
1717

18+
* You must upgrade {product-title} to version 4.6.30, 4.7.11, or higher before upgrading to {ServerlessProductName} 1.16.0.
19+
1820
* The AMQ Streams Operator might prevent the installation or upgrade of the {ServerlessOperatorName}. If this happens, the following error is thrown by Operator Lifecycle Manager (OLM):
1921
+
2022
[source,terminal]
@@ -120,3 +122,8 @@ spec:
120122
* 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`.
121123
+
122124
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`.
125+
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+
+
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

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

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
[id="serverless-rn-1-17-0_{context}"]
2+
= Release Notes for Red Hat {ServerlessProductName} 1.17.0
3+
4+
[id="new-features-1-17-0_{context}"]
5+
== New features
6+
7+
* {ServerlessProductName} now uses Knative Serving 0.23.0.
8+
* {ServerlessProductName} now uses Knative Eventing 0.23.0.
9+
* {ServerlessProductName} now uses Kourier 0.23.0.
10+
* {ServerlessProductName} now uses Knative `kn` CLI 0.23.0.
11+
* {ServerlessProductName} now uses Knative Kafka 0.23.0.
12+
* The `kn func` CLI plug-in now uses `func` 0.17.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 definition (CRD):
16+
+
17+
[source,yaml]
18+
----
19+
...
20+
spec:
21+
config:
22+
network:
23+
defaultExternalScheme: "http"
24+
...
25+
----
26+
27+
* mTLS functionality is now Generally Available (GA).
28+
29+
* TypeScript templates are now available when you create a function using `kn func`.
30+
31+
* Changes to API versions in Knative Eventing 0.23.0:
32+
33+
** The `v1alpha1` version of the `KafkaChannel` API, which was deprecated in {ServerlessProductName} version 1.14.0, has been removed. If the `ChannelTemplateSpec` parameters of your config maps contain references to this older version, you must update this part of the spec to use the correct API version.
34+
35+
[id="fixed-issues-1-17-0_{context}"]
36+
== Fixed issues
37+
38+
[id="known-issues-1-17-0_{context}"]
39+
== Known issues
40+
41+
* If you try to use an older version of the Knative `kn` CLI with a newer {ServerlessProductName} release, the API is not found and an error occurs.
42+
+
43+
For example, if you use the 1.16.0 release of the `kn` CLI, which uses version 0.22.0, with the 1.17.0 {ServerlessProductName} release, which uses the 0.23.0 versions of the Knative Serving and Knative Eventing APIs, the CLI does not work because it continues to look for the outdated 0.22.0 API versions.
44+
+
45+
Ensure that you are using the latest `kn` CLI version for your {ServerlessProductName} release to avoid issues.
46+
47+
* Kafka channel metrics are not monitored or shown in the corresponding web console dashboard in this release. This is due to a breaking change in the Kafka dispatcher reconciling process.
48+
49+
* 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.
50+
+
51+
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.
52+
// add KB article link when ready

‎serverless/admin_guide/serverless-ossm-setup.adoc‎

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,6 @@ The {ServerlessOperatorName} provides Kourier as the default ingress for Knative
2222

2323
Integrating {ProductShortName} with {ServerlessProductName} natively, without Kourier, allows you to use additional networking and routing options that are not supported by the default Kourier ingress, such as mTLS functionality.
2424

25-
:FeatureName: mTLS for {ServerlessProductName}
26-
include::modules/technology-preview.adoc[leveloffset=+2]
27-
2825
The examples in the following procedures use the domain `example.com`. The example certificate for this domain is used as a certificate authority (CA) that signs the subdomain certificate.
2926

3027
To complete and verify these procedures in your deployment, you need either a certificate signed by a widely trusted public CA or a CA provided by your organization. Example commands must be adjusted according to your domain, subdomain, and CA.

‎serverless/cli_tools/installing-kn.adoc‎

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,19 @@ include::modules/common-attributes.adoc[]
66

77
toc::[]
88

9-
[NOTE]
10-
====
119
The Knative CLI (`kn`) does not have its own login mechanism. To log in to the cluster, you must install the `oc` CLI and use the `oc login` command.
1210

1311
Installation options for the `oc` CLI will vary depending on your operating system.
1412

1513
For more information on installing the `oc` CLI for your operating system and logging in with `oc`, see the xref:../../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[OpenShift CLI getting started] documentation.
14+
15+
[IMPORTANT]
16+
====
17+
If you try to use an older version of the Knative `kn` CLI with a newer {ServerlessProductName} release, the API is not found and an error occurs.
18+
19+
For example, if you use the 1.16.0 release of the `kn` CLI, which uses version 0.22.0, with the 1.17.0 {ServerlessProductName} release, which uses the 0.23.0 versions of the Knative Serving and Knative Eventing APIs, the CLI does not work because it continues to look for the outdated 0.22.0 API versions.
20+
21+
Ensure that you are using the latest `kn` CLI version for your {ServerlessProductName} release to avoid issues.
1622
====
1723

1824
include::modules/serverless-installing-cli-web-console.adoc[leveloffset=+1]

‎serverless/serverless-release-notes.adoc‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,14 @@ For an overview of {ServerlessProductName} functionality, see xref:../serverless
1515
For details about the latest Knative component releases, see the link:https://knative.dev/blog/releases[Knative releases blog].
1616
====
1717

18+
include::modules/serverless-api-versions.adoc[leveloffset=+1]
19+
1820
// Modules included, most to least recent
21+
include::modules/serverless-rn-1-17-0.adoc[leveloffset=+1]
1922
include::modules/serverless-rn-1-16-0.adoc[leveloffset=+1]
2023
include::modules/serverless-rn-1-15-0.adoc[leveloffset=+1]
24+
// No longer supported
2125
include::modules/serverless-rn-1-14-0.adoc[leveloffset=+1]
22-
// delete older relnotes?
2326
include::modules/serverless-rn-1-13-0.adoc[leveloffset=+1]
2427
include::modules/serverless-rn-1-12-0.adoc[leveloffset=+1]
2528
include::modules/serverless-rn-1-11-0.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)