|
| 1 | +// Module included in the following assemblies |
| 2 | +// |
| 3 | +// * about/serverless-release-notes.adoc |
| 4 | + |
| 5 | +:_content-type: REFERENCE |
| 6 | +[id="serverless-rn-1-34-0_{context}"] |
| 7 | += Red Hat {ServerlessProductName} 1.34 |
| 8 | + |
| 9 | +{ServerlessProductName} 1.34 is now available. New features, updates, and known issues that pertain to {ServerlessProductName} on {ocp-product-title} are included in the following notes: |
| 10 | + |
| 11 | +[id="new-features-1-34-0_{context}"] |
| 12 | +== New features |
| 13 | + |
| 14 | +* {ServerlessProductName} now uses Knative Serving 1.14. |
| 15 | +* {ServerlessProductName} now uses Knative Eventing 1.14. |
| 16 | +* {ServerlessProductName} now uses Kourier 1.14. |
| 17 | +* {ServerlessProductName} now uses Knative (`kn`) CLI 1.14. |
| 18 | +* {ServerlessProductName} now uses Knative for Apache Kafka 1.14. |
| 19 | +* The `kn func` CLI plugin now uses `func` 1.15. |
| 20 | + |
| 21 | +* {ServerlessLogicProductName} now supports multiple configuration for OpenAPI within the same namespace. |
| 22 | + |
| 23 | +* The management console for {ServerlessLogicProductName} is now available as a Technology Preview (TP) feature for streamlining the development process. |
| 24 | + |
| 25 | +* {ServerlessLogicProductName} 1.34 introduces a new feature that allows workflows to access different {ocp-product-title} clusters through configuration. This feature enables users to define REST calls within a workflow to seamlessly interact with multiple clusters. |
| 26 | + |
| 27 | +* In {ServerlessLogicProductName}, the Job Service liveness checks is now enhanced to limit the time required to retrieve the leader status. A new system property, `kogito.jobs-service.management.leader-check.expiration-in-seconds`, has been introduced, allowing you to configure the maximum time allowed for the leader status check. |
| 28 | + |
| 29 | +* Automatic `EventType` registration is an Eventing feature is now available as a Technology Preview (TP). It automatically creates `EventTypes` objects based on processed events on the broker ingress and in-memory channels, improving the experience of consuming and creating `EventTypes`. |
| 30 | + |
| 31 | +* Encryption Serving is now available as a Technology Preview (TP) feature. |
| 32 | + |
| 33 | +* Startup probes are now supported, helping to reduce cold start times for faster application startup and improved performance. These probes are particularly useful for containers with slow startup processes. |
| 34 | + |
| 35 | +* {ServerlessProductName} Serving transport encryption feature allows transporting data over secured and encrypted HTTPS connections using TLS. This is now available as a Technology Preview (TP) feature. |
| 36 | + |
| 37 | +* Go functions using S2I builder are now available as a Technology Preview (TP) feature for Linux and Mac developers, allowing them to implement and build Go functions on these platforms. |
| 38 | + |
| 39 | +* Multi-container support for Knative Serving allows you to use a single Knative service to deploy a multi-container pod. It also supports the `readiness` and `liveness` probe values for multiple containers. |
| 40 | + |
| 41 | +* Autoscaling for Knative Kafka triggers is now enhanced with KEDA (Kubernetes Event-Driven Autoscaling) as a Technology Preview (TP). Autoscaling using CMA/KEDA further enhances performance by optimizing resource allocation for Kafka triggers and `KafkaSource` objects, ensuring better scalability in event-driven workloads. |
| 42 | + |
| 43 | +* Knative Eventing now offers support for data in transit encryption (Eventing TLS) as a Technology Preview (TP) feature. You can configure Knative Eventing components to expose HTTPS addresses as well as add user-provided CA trust bundles to clients. |
| 44 | + |
| 45 | +[id="fixed-issues-1-34-0_{context}"] |
| 46 | +== Fixed issues |
| 47 | + |
| 48 | +* Previously, `KafkaSource` objects would incorrectly remain in the `Ready` status even when the `KafkaSource.spec.net.tls.key` failed to load. This issue has been resolved. An error is now reported when creating a Kafka `Broker`, `KafkaChannel`, `KafkaSource`, or `KafkaSink` object with unsupported TLS certificates in PKCS #1 (Public-Key Cryptography Standards #1) format, ensuring proper handling and notification of configuration issues. |
| 49 | + |
| 50 | +* The Eventing controller incorrectly requeued the wrong object type (`Namespace`), causing "resource not found" log errors. This issue is now resolved, and the controller now handles object requeuing, ensuring more accurate logging and resource management. |
0 commit comments