Skip to content

Commit 62bf534

Browse files
committed
SRVCOM-1661: release notes and build error fix
1 parent 75cb2ce commit 62bf534

File tree

5 files changed

+60
-12
lines changed

5 files changed

+60
-12
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,12 @@
1919
* The `kn func` CLI plug-in now uses `func` 0.20.
2020

2121
* The Kafka broker is now available as a Technology Preview.
22+
+
23+
[IMPORTANT]
24+
====
25+
The Kafka broker, which is currently in Technology Preview, is not supported on FIPS.
26+
====
27+
2228
* The `kn event` plug-in is now available as a Technology Preview.
2329

2430
[id="known-issues-1-20-0_{context}"]

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

Lines changed: 39 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,19 +11,49 @@
1111
[id="new-features-1-21-0_{context}"]
1212
== New features
1313

14-
* {ServerlessProductName} now uses Knative Serving 0.27.
15-
* {ServerlessProductName} now uses Knative Eventing 0.27.
16-
* {ServerlessProductName} now uses Kourier 0.27.
17-
* {ServerlessProductName} now uses Knative `kn` CLI 0.27.
18-
* {ServerlessProductName} now uses Knative Kafka 0.27.
14+
* {ServerlessProductName} now uses Knative Serving 1.0
15+
* {ServerlessProductName} now uses Knative Eventing 1.0.
16+
* {ServerlessProductName} now uses Kourier 1.0.
17+
* {ServerlessProductName} now uses Knative `kn` CLI 1.0.
18+
* {ServerlessProductName} now uses Knative Kafka 1.0.
1919
* The `kn func` CLI plug-in now uses `func` 0.21.
20-
// check versions
21-
* The Knative open source project has begun to deprecate camel-cased configuration keys in favor of using kebab-cased keys consistently. As a result, the `defaultExternalScheme` key, previously mentioned in the {ServerlessProductName} 1.18.0 release notes, has been deprecated and replaced by the `default-external-scheme` key. Usage instructions for the key remain the same.
20+
* The Kafka sink is now available as a Technology Preview.
21+
22+
* The Knative open source project has begun to deprecate camel-cased configuration keys in favor of using kebab-cased keys consistently. As a result, the `defaultExternalScheme` key, previously mentioned in the {ServerlessProductName} 1.18.0 release notes, is now deprecated and replaced by the `default-external-scheme` key. Usage instructions for the key remain the same.
2223

2324
[id="fixed-issues-1-21-0_{context}"]
2425
== Fixed issues
25-
// add a version, e.g. 1-20-0
26+
27+
* In {ServerlessProductName} 1.20.0, there was an event delivery issue affecting the use of `kn event send` to send events to a service. This issue is now fixed.
28+
29+
* In {ServerlessProductName} 1.20.0 (`func` 0.20), TypeScript functions created with the `http` template failed to deploy on the cluster. This issue is now fixed.
30+
31+
* In {ServerlessProductName} 1.20.0 (`func` 0.20), deploying a function using the `gcr.io` registry failed with an error. This issue is now fixed.
32+
33+
* In {ServerlessProductName} 1.20.0 (`func` 0.20), creating a Springboot function project directory with the `kn func create` command and then running the `kn func build` command failed with an error message. This issue is now fixed.
34+
35+
* In {ServerlessProductName} 1.19.0 (`func` 0.19), some runtimes were unable to build a function by using podman. This issue is now fixed.
2636

2737
[id="known-issues-1-21-0_{context}"]
2838
== Known issues
29-
// add a version, e.g. 1-20-0
39+
40+
* Currently, the domain mapping controller cannot process the URI of a broker, which contains a path that is currently not supported.
41+
+
42+
This means that, if you want to use a `DomainMapping` custom resource (CR) to map a custom domain to a broker, you must configure the `DomainMapping` CR with the broker's ingress service, and append the exact path of the broker to the custom domain:
43+
+
44+
.Example `DomainMapping` CR
45+
[source,yaml]
46+
----
47+
apiVersion: serving.knative.dev/v1alpha1
48+
kind: DomainMapping
49+
metadata:
50+
name: <domain-name>
51+
namespace: knative-eventing
52+
spec:
53+
ref:
54+
name: broker-ingress
55+
kind: Service
56+
apiVersion: v1
57+
----
58+
+
59+
The URI for the broker is then `<domain-name>/<broker-namespace>/<broker-name>`.

serverless/develop/serverless-kafka-developer.adoc

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,13 @@ toc::[]
99

1010
Knative Kafka functionality is available in an {ServerlessProductName} installation xref:../../serverless/admin_guide/serverless-kafka-admin.adoc#serverless-install-kafka-odc_serverless-kafka-admin[if a cluster administrator has installed the `KnativeKafka` custom resource].
1111

12+
// OCP
13+
ifdef::openshift-enterprise[]
1214
[NOTE]
1315
====
1416
Knative Kafka is not currently supported for IBM Z and IBM Power.
1517
====
18+
endif::[]
1619

1720
Knative Kafka provides additional options, such as:
1821

@@ -43,10 +46,15 @@ include::modules/serverless-kafka-source-yaml.adoc[leveloffset=+2]
4346
[id="serverless-kafka-developer-broker"]
4447
== Kafka broker
4548

49+
If a cluster administrator has configured your {ServerlessProductName} deployment to use Kafka broker as the default broker type, xref:../../serverless/develop/serverless-using-brokers.adoc#serverless-using-brokers-creating-brokers[creating a broker by using the default settings] creates a Kafka-based `Broker` object. If your {ServerlessProductName} deployment is not configured to use Kafka broker as the default broker type, you can still use the following procedure to create a Kafka-based broker.
50+
4651
:FeatureName: Kafka broker
4752
include::snippets/technology-preview.adoc[leveloffset=+2]
4853

49-
If a cluster administrator has configured your {ServerlessProductName} deployment to use Kafka broker as the default broker type, xref:../../serverless/develop/serverless-using-brokers.adoc#serverless-using-brokers-creating-brokers[creating a broker by using the default settings] creates a Kafka-based `Broker` object. If your {ServerlessProductName} deployment is not configured to use Kafka broker as the default broker type, you can still use the following procedure to create a Kafka-based broker.
54+
[IMPORTANT]
55+
====
56+
The Kafka broker, which is currently in Technology Preview, is not supported on FIPS.
57+
====
5058

5159
include::modules/serverless-kafka-broker.adoc[leveloffset=+2]
5260

serverless/install/install-serverless-operator.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,13 @@ Read the following information about supported configurations and prerequisites
1818
* {ServerlessProductName} is supported for installation in a restricted network environment.
1919
2020
* {ServerlessProductName} currently cannot be used in a multi-tenant configuration on a single cluster.
21-
endif::[]
2221
2322
include::modules/serverless-cluster-sizing-req.adoc[leveloffset=+2]
23+
endif::[]
24+
25+
ifdef::openshift-dedicated[]
26+
include::modules/serverless-cluster-sizing-req.adoc[leveloffset=+1]
27+
endif::[]
2428

2529
ifdef::openshift-enterprise[]
2630
[id="install-serverless-operator-scaling-with-machinesets"]

serverless/serverless-release-notes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ include::modules/serverless-deprecated-removed-features.adoc[leveloffset=+1]
2424

2525
// Release notes included, most to least recent
2626
// OCP + OSD
27-
// include::modules/serverless-rn-1-21-0.adoc[leveloffset=+1]
27+
include::modules/serverless-rn-1-21-0.adoc[leveloffset=+1]
2828
include::modules/serverless-rn-1-20-0.adoc[leveloffset=+1]
2929

3030
// OCP only

0 commit comments

Comments
 (0)