|
| 1 | +// Module included in the following assemblies |
| 2 | +// |
| 3 | +// * about/serverless-release-notes.adoc |
| 4 | + |
| 5 | +:_content-type: REFERENCE |
| 6 | +[id="serverless-rn-1-36-0_{context}"] |
| 7 | += Red Hat {ServerlessProductName} 1.36 |
| 8 | + |
| 9 | +{ServerlessProductName} 1.36 is now available. New features, updates, fixed issues, and known issues that pertain to {ServerlessProductName} on {ocp-product-title} are included in the following notes: |
| 10 | + |
| 11 | +[id="new-features-1-36-0_{context}"] |
| 12 | +== New features |
| 13 | + |
| 14 | +[id="new-features-eventing-1-36-0_{context}"] |
| 15 | +=== {ServerlessProductName} Eventing |
| 16 | + |
| 17 | +* {ServerlessProductName} now uses Knative Eventing 1.16. |
| 18 | + |
| 19 | +* {ServerlessProductName} now uses Knative for Apache Kafka 1.16. |
| 20 | + |
| 21 | +* `IntegrationSource` and `IntegrationSink` are now available as a Technology Preview. These are Knative Eventing custom resources that support selected Kamelets from the Apache Camel project. Kamelets enables you to connect to third-party systems for improved connectivity, acting as either sources (event producers) or sinks (event consumers). |
| 22 | + |
| 23 | +* Knative Eventing can now automatically discover and register EventTypes based on the structure of incoming events. This feature simplifies the configuration and management of EventTypes, reducing the need for manual definitions. This feature is available as a Technology Preview. |
| 24 | + |
| 25 | +* {ServerlessProductName} Eventing introduces `EventTransform`, a new API resource that you can use to declaratively transform JSON events without writing custom code. With `EventTransform`, you can modify attributes, extract or reshape data, and streamline event flows across systems. Common use cases include event enrichment, format conversion, and request-response transformation. `EventTransform` integrates seamlessly with Knative sources, triggers, and brokers, enhancing interoperability in event-driven architectures. This feature is now available as a Technology Preview. |
| 26 | ++ |
| 27 | + |
| 28 | +See the following key features of `EventTransform`: |
| 29 | + |
| 30 | +** Define transformations declaratively using Kubernetes-native resources |
| 31 | +** Use JSONata expressions for advanced and flexible event data manipulation |
| 32 | +** Easily insert transformations at any point within event-driven workflows |
| 33 | +** Support for transforming both sink-bound and reply events for better routing control |
| 34 | + |
| 35 | +* The `sinks.knative.dev` API group has now been added to the `ClusterRoles` namespace in Knative Eventing. Developers now have permissions to `get`, `list`, and `watch` resources in this API group, improving accessibility and integration with sink resources. |
| 36 | + |
| 37 | +* Transport encryption for Knative Eventing is now available as a Generally Available (GA) feature. |
| 38 | + |
| 39 | +* Knative Eventing now supports the ability to define authorization policies that restrict which entities can send events to Eventing custom resources. This enables greater control and security within event-driven architectures. This functionality is available as a Developer Preview. |
| 40 | + |
| 41 | +* Knative Eventing catalog is now integrated into the {RHDHProductName} through the Event Catalog plugin for Backstage. This integration enables users to discover and explore Knative Eventing resources directly within the {RHDHProductName} interface. This functionality is available as a Developer Preview. |
| 42 | + |
| 43 | +* The `KafkaSource` API has now been promoted to version `v1`, signaling its stability and readiness for production use. |
| 44 | + |
| 45 | +* {ServerlessProductName} now supports deployment on ARM architecture as a Generally Available (GA) feature. |
| 46 | + |
| 47 | +* The `kn event` plugin is now available as a GA feature. You can use this plugin to send events directly from the command line to various destinations, streamlining event-driven application development and testing workflows. |
| 48 | + |
| 49 | +[id="new-features-serving-1-36-0_{context}"] |
| 50 | +=== {ServerlessProductName} Serving |
| 51 | + |
| 52 | +* {ServerlessProductName} now uses Knative Serving 1.16. |
| 53 | + |
| 54 | +* {ServerlessProductName} now uses Kourier 1.16. |
| 55 | + |
| 56 | +* {ServerlessProductName} now uses Knative (`kn`) CLI 1.16. |
| 57 | + |
| 58 | +[id="new-features-functions-1-36-0_{context}"] |
| 59 | +=== {ServerlessProductName} Functions |
| 60 | + |
| 61 | +* The `kn func` CLI plugin now uses `func` 1.16. |
| 62 | + |
| 63 | +* {ServerlessProductName} Functions support integration with Cert Manager, enabling automated certificate management for the function workloads. This functionality is available as a Developer Preview. |
| 64 | + |
| 65 | +[id="new-features-osl-1-36-0_{context}"] |
| 66 | +=== {ServerlessLogicProductName} |
| 67 | + |
| 68 | +* When starting a workflow via HTTP, you can now include additional properties alongside the `workflowdata` field in the request body. These extra fields are ignored by the runtime but are available in the Data Index as process variables as shown in the following example: |
| 69 | ++ |
| 70 | +[source,json] |
| 71 | +---- |
| 72 | +{"workflowdata": {"name": "John"}, "groupKey": "follower"} |
| 73 | +---- |
| 74 | + |
| 75 | +* You can now filter workflow instances by the content of workflow variables using GraphQL queries on `ProcessInstances.variables`. For example, the following query retrieves process instances where the `language` field in `workflowdata` equals `Spanish`: |
| 76 | ++ |
| 77 | +[source,terminal] |
| 78 | +---- |
| 79 | +ProcessInstances (where:{variables:{workflowdata:{language:{equal:Spanish}}}}) { |
| 80 | + variables, |
| 81 | + state, |
| 82 | + lastUpdate, |
| 83 | + nodes { |
| 84 | + name |
| 85 | + } |
| 86 | +} |
| 87 | +---- |
| 88 | + |
| 89 | +* {ServerlessLogicProductName} Data Index now supports filtering queries by using workflow definition metadata. |
| 90 | + |
| 91 | +* {ServerlessLogicOperatorName} now emits events to the Data Index to indicate when a workflow definition becomes available or unavailable. |
| 92 | + |
| 93 | +[id="fixed-issues-1-36-0_{context}"] |
| 94 | +== Fixed issues |
| 95 | + |
| 96 | +[id="fixed-issues-eventing-1-36-0_{context}"] |
| 97 | +=== {ServerlessProductName} Eventing |
| 98 | + |
| 99 | +* Previously, the Knative Kafka dispatcher could stop consuming events if a Kafka consumer group rebalance occurred while a sink was processing events out of order. This behavior triggered the following errors: |
| 100 | + |
| 101 | +** `SEVERE: Unhandled exception` |
| 102 | +** `java.lang.IndexOutOfBoundsException: bitIndex < 0` |
| 103 | +** Repeated logs like `Request joining group due to: group is already rebalancing` |
| 104 | + |
| 105 | ++ |
| 106 | + |
| 107 | +This issue is now fixed. The dispatcher correctly handles out-of-order event consumption during rebalancing and continues processing events without interruption. |
| 108 | + |
| 109 | +* Previously, a KafkaSource remained in a `Ready` state even when `KafkaSource.spec.net.tls.key` failed to load due to the use of unsupported TLS certificates in PKCS #1 format. This issue is now fixed. An appropriate error is now reported when attempting to create a `KafkaBroker`, `KafkaChannel`, `KafkaSource`, or `KafkaSink` using TLS certificates in an unsupported format. |
| 110 | + |
| 111 | +[id="known-issues-1-36-0_{context}"] |
| 112 | +== Known issues |
| 113 | + |
| 114 | +[id="known-issues-osl-1-36-0_{context}"] |
| 115 | +=== {ServerlessLogicProductName} |
| 116 | + |
| 117 | +* If the `swf-dev-mode` image is started with a broken or invalid workflow definition, the container might enter a stuck state. |
| 118 | + |
| 119 | +* When deploying a workflow in the `preview` profile on {ocp-product-title}, if the initial build fails and is later corrected, the Operator does not create the corresponding workflow deployment. As a result, the deployment remains missing and the `SonataFlow` status is not updated, even after the build is fixed. |
| 120 | + |
| 121 | +* The {ServerlessLogicProductName} builder image consistently downloads the `plexus-utils-1.1` artifact during the build process, regardless of local caching or dependency resolution settings. |
| 122 | + |
| 123 | +* When running images in disconnected or restricted network environments, the Maven wrapper might experience timeouts while attempting to download required components. |
| 124 | + |
| 125 | +* The `openshift-serverless-1/logic-swf-builder-rhel8:1.35.0` and `openshift-serverless-1/logic-swf-builder-rhel8:1.36.0` images are currently downloading the persistence extensions from Maven during the build process. |
0 commit comments