|
11 | 11 | [id="new-features-1-21-0_{context}"] |
12 | 12 | == New features |
13 | 13 |
|
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. |
19 | 19 | * 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. |
22 | 23 |
|
23 | 24 | [id="fixed-issues-1-21-0_{context}"] |
24 | 25 | == 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. |
26 | 36 |
|
27 | 37 | [id="known-issues-1-21-0_{context}"] |
28 | 38 | == 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>`. |
0 commit comments