Release notes

Previously, post-install batch jobs were removed after a certain period, leaving privileged service accounts unbound. This caused compliance systems to flag the issue. The problem has been resolved by retaining completed jobs, ensuring that service accounts remain bound.

OpenShift Serverless now uses Knative Serving 1.11.

OpenShift Serverless now uses Knative Eventing 1.11.

OpenShift Serverless now uses Kourier 1.11.

OpenShift Serverless now uses Knative (kn) CLI 1.11.

OpenShift Serverless now uses Knative for Apache Kafka 1.11.

The kn func CLI plugin now uses func 1.13.

Serverless Logic, which is available as a Technology Preview (TP) feature, has been updated.

You can configure the OpenShift Serverless Functions readiness and liveness probe settings for the user container and queue-proxy container.

OpenShift Serverless Functions now supports OpenShift Pipelines versions from 1.10 till 1.14 (latest). The older versions of OpenShift Pipelines are no longer compatible with OpenShift Serverless Functions.

On-cluster function building, including using Pipelines as Code is now supported on IBM zSystems (s390x) and IBM Power (ppc64le) on OpenShift Data Foundation storage only.

You can now subscribe a function to a set of events by using the func subscribe command. This links your function to CloudEvent objects defined by your filters and enables automated responses.

The Knative Serving TLS encryption feature for internal traffic is now deprecated. It was a Tech Preview feature. The functionality with the internal-encryption configuration flag is no longer available and it will be replaced by new configuration flags in a future release.

The secret filtering is enabled by default on the OpenShift Serverless Operator side. An environment variable ENABLE_SECRET_INFORMER_FILTERING_BY_CERT_UID=true, is added by default to the net-istio and net-kourier controller pods.

The domain-mapping and domain-mapping-webhook deployments functionality in the knative-serving namespace is now removed. They are now integrated with Serving Webhook and Serving Controller.

If you set spec.config.domain field in the KnativeServing custom resource (CR), the default external domain will no longer auto-populates the config-domain config map in the knative-serving namespace. Now, you must configure the config-domain config map manually to ensure accurate domain settings.

You can now use the gRPC health probe for net-kourier deployments. The the Kourier Controller now uses a standard Kubernetes gRPC health probe for both readiness and liveness, replacing its previous use of exec and custom commands. The timeoutSeconds value has been adjusted from 100 milliseconds to 1 second to ensure more reliable probe responses.

The new trigger filters feature is now available as a Technology Preview. The new trigger filters are now enabled by default. It allows users to specify a set of filter expressions, where each expression evaluates to either true or false for each event.

Knative Eventing now offers support for data in transit encryption (Eventing TLS) as a developer preview. You can configure Knative Eventing components to expose HTTPS addresses as well as add user-provided CA trust bundles to clients.

OpenShift Serverless now supports custom OpenShift CA bundle injection for system components. For more information, see Configuring a custom PKI.

You can now use the Custom Metrics Autoscaler Operator to autoscale Knative Eventing sources for Apache Kafka sources. This functionality is available as a developer preview, offering enhanced scalability and efficiency for Kafka-based event sources within Knative Eventing.

You can now explore the Knative Eventing monitoring dashboards directly within the Observe tab of the Developer view in the OpenShift Developer Console.

The support for EventTypes v1beta1 in Knative shipped is deprecated in OpenShift Serverless 1.32. In OpenShift Serverless 1.32, the Knative CLI uses the EventType v1beta2 API to facilitate the new reference model. In previous releases, the kn CLI is not backward compatible with the EventType API v1beta1 and is limited to the kn eventtypes sub-commands group. Therefore, it is recommended to use a matching kn version for the best user experience.

The default CPU limit is now increased for 3scale-kourier-gateways from 500m to 1s. When more than 500 Knative Service instances are created, it could lead to readiness and liveness probe failures in the 3scale-kourier-gateways pod due to CPU resource exhaustion. This adjustment aims to reduce such failures and ensures smoother operation even under heavy loads.

Due to different mount point permissions, direct upload on a cluster build does not work on IBM zSystems (s390x) and IBM Power (ppc64le).

Building and deploying a function using Podman version 4.6 fails with the invalid pull policy "1" error.

OpenShift Serverless now uses Knative Serving 1.10.

OpenShift Serverless now uses Knative Eventing 1.10.

OpenShift Serverless now uses Kourier 1.10.

OpenShift Serverless now uses Knative (kn) CLI 1.10.

OpenShift Serverless now uses Knative for Apache Kafka 1.10.

The kn func CLI plug-in now uses func 1.11.

OpenShift Serverless multi-tenancy with Service Mesh is now available as a Technology Preview (TP) feature.

Serverless Logic, which is available as a Technology Preview (TP) feature, has been updated.

OpenShift Serverless can now be installed and used on single-node OpenShift.

You can now configure a persistent volume claim (PVC) for an existing PersistentVolume object to use with a Serverless function.

When specifying Kourier for Ingress and using DomainMapping, the TLS for OpenShift Route is set to passthrough, and TLS is handled by the Kourier Gateway. Beginning with Serverless 1.31, it is possible to specify the enabled cipher suites on the side of the Kourier Gateway.

Integrating Red Hat OpenShift Service Mesh with Serverless when Kourier is enabled is now deprecated. Use net-istio instead of net-kourier for Service Mesh integration.

The PodDistruptionBudget and HorizontalPodAutoscaler objects have been added for the 3scale-kourier-gateway deployment.

Now you can change the pattern for Apache Kafka topic names used by Knative brokers and channels for Apache Kafka.

The DomainMapping v1alpha1 custom resource definition (CRD) is now deprecated. Use v1beta1 CRD instead.

The NamespacedKafka annotation, which was a Technology Preview (TP) feature, is now deprecated in favor of the standard Kafka broker with no data plane isolation.

Previously, when deploying Knative Eventing with full Red Hat OpenShift Service Mesh integration and with STRICT peer authentication, the PingSource adapter metrics were unavailable.

OpenShift Serverless now uses Knative Serving 1.9.

OpenShift Serverless now uses Knative Eventing 1.9.

OpenShift Serverless now uses Kourier 1.9.

OpenShift Serverless now uses Knative (kn) CLI 1.9.

OpenShift Serverless now uses Knative for Apache Kafka 1.9.

The kn func CLI plug-in now uses func 1.10.1.

OpenShift Serverless now runs on HyperShift-hosted clusters.

OpenShift Serverless now runs on single-node OpenShift.

Developer Experience around OpenShift Serverless is now available through OpenShift Toolkit, an OpenShift IDE Extension for the Visual Studio Code (VSCode). The extension can be installed from the VSCode Extension Tab and VSCode Marketplace. See the Marketplace page for the Visual Studio Code OpenShift Toolkit extension.

OpenShift Serverless Functions nows supports Red Hat OpenShift Pipelines versions 1.10 and 1.11. Older versions of Red Hat OpenShift Pipelines are no longer compatible with OpenShift Serverless Functions.

Serverless Logic is now available as a Technology Preview (TP) feature.

Beginning with OpenShift Serverless 1.30.0, the following runtime environments are supported on IBM zSystems using the s2i builder:

Eventing integration with Red Hat OpenShift Service Mesh is now available as a Technology Preview (TP) feature.

Pipelines-as-code for OpenShift Serverless Functions is now available as a Technology Preview (TP).

You can now configure the burst and queries per second (QPS) values for net-kourier.

OpenShift Serverless Functions users now have the ability to override the readiness and liveness probe values in the func.yaml file for individual Quarkus functions.

Beginning with OpenShift Serverless 1.30.0, Kourier controller and gateway manifests have the following limits and requests by default:

The NamespacedKafka annotation, which was a Technology Preview (TP) feature, is now deprecated in favor of the standard Kafka broker with no data plane isolation.

Previously, the 3scale-kourier-gateway pod was sending thousands of net-kourier-controller DNS queries daily. New queries were being sent for each NXDOMAIN reply. This continued until the correct DNS query was produced.

Building and deploying a function using Podman version 4.6 fails with the invalid pull policy "1" error.

On-cluster function building, including using Pipelines-as-code, is not supported on IBM zSystems and IBM Power.

Buildpack builder is not supported on IBM zSystems and IBM Power.

Previously, the net-kourier-controller sometimes failed to start due to the liveness probe error. This has been fixed.

OpenShift Serverless now uses Knative Serving 1.8.

OpenShift Serverless now uses Knative Eventing 1.8.

OpenShift Serverless now uses Kourier 1.8.

OpenShift Serverless now uses Knative (kn) CLI 1.8.

OpenShift Serverless now uses Knative for Apache Kafka 1.8.

The kn func CLI plug-in now uses func 1.10.

Beginning with OpenShift Serverless 1.29, the different product versions are available as follows:

You can now create OpenShift Serverless functions through developer console using OpenShift Container Platform Pipelines.

Multi-container support for Knative Serving is now generally available (GA). This feature allows you to use a single Knative service to deploy a multi-container pod.

OpenShift Serverless functions can now override the readiness and liveness probe values in the func.yaml file for individual Node.js and TypeScript functions.

You can now configure your function to re-deploy automatically to the cluster when its source code changes in the GitHub repository. This allows for more seamless CI/CD integration.

Eventing integration with Service Mesh is now available as developer preview feature. The integration includes: PingSource, ApiServerSource, Knative Source for Apache Kafka, Knative Broker for Apache Kafka, Knative Sink for Apache Kafka, ContainerSource, and SinkBinding.

This release includes the upgraded Developer Preview for OpenShift Serverless Logic.

API version v1alpha1 of the Knative Operator Serving and Eventings CRDs has been removed. You need to use the v1beta1 version instead. This does not affect the existing installations, because CRDs are updated automatically when upgrading the Serverless Operator.

When updating the secret specified in DomainMapping, simply updating the secret does not trigger the reconcile loop. You need to either rename the secret or delete the Knative Ingress resource to trigger the reconcile loop.

Webhook Horizontal Pod Autoscaler (HPA) settings are overridden by the OpenShift Serverless Operator. As a result, it fails to scale for higher workloads. To work around this issue, manually set the initial replica value that corresponds to your workload.

KafkaSource resources created before Red Hat OpenShift Serverless 1.27 get stuck when being deleted. To work around the issue, after starting to delete a KafkaSource, remove the finalizer from the resource.

The net-kourier-controller might not be able to start due to the liveness probe error. You can work around the problem using the Knowledgebase solution.

OpenShift Serverless now uses Knative Serving 1.7.

OpenShift Serverless now uses Knative Eventing 1.7.

OpenShift Serverless now uses Kourier 1.7.

OpenShift Serverless now uses Knative (kn) CLI 1.7.

OpenShift Serverless now uses Knative broker implementation for Apache Kafka 1.7.

The kn func CLI plug-in now uses func 1.9.1 version.

Node.js and TypeScript runtimes for OpenShift Serverless Functions are now Generally Available (GA).

Python runtime for OpenShift Serverless Functions is now available as a Technology Preview.

Multi-container support for Knative Serving is now available as a Technology Preview. This feature allows you to use a single Knative service to deploy a multi-container pod.

In OpenShift Serverless 1.29 or later, the following components of Knative Eventing will be scaled down from two pods to one:

The serverless.openshift.io/enable-secret-informer-filtering annotation for the Serving CR is now deprecated. The annotation is valid only for Istio, and not for Kourier.

Currently, runtimes for Python are not supported for OpenShift Serverless Functions on IBM Power, IBM zSystems, and IBM® LinuxONE.

On the Windows platform, Python functions cannot be locally built, run, or deployed using the Source-to-Image builder due to the app.sh file permissions.

KafkaSource resources created before Red Hat OpenShift Serverless 1.27 get stuck when being deleted. To work around the issue, after starting to delete a KafkaSource, remove the finalizer from the resource.

OpenShift Serverless now uses Knative Serving 1.6.

OpenShift Serverless now uses Knative Eventing 1.6.

OpenShift Serverless now uses Kourier 1.6.

OpenShift Serverless now uses Knative (kn) CLI 1.6.

OpenShift Serverless now uses Knative Kafka 1.6.

The kn func CLI plug-in now uses func 1.8.1.

Namespace-scoped brokers are now available as a Technology Preview. Such brokers can be used, for instance, to implement role-based access control (RBAC) policies.

KafkaSink now uses the CloudEvent binary content mode by default. The binary content mode is more efficient than the structured mode because it uses headers in its body instead of a CloudEvent. For example, for the HTTP protocol, it uses HTTP headers.

You can now use the gRPC framework over the HTTP/2 protocol for external traffic using the OpenShift Route on OpenShift Container Platform 4.10 and later. This improves efficiency and speed of the communications between the client and server.

API version v1alpha1 of the Knative Operator Serving and Eventings CRDs is deprecated in 1.27. It will be removed in future versions. Red Hat strongly recommends to use the v1beta1 version instead. This does not affect the existing installations, because CRDs are updated automatically when upgrading the Serverless Operator.

The delivery timeout feature is now enabled by default. It allows you to specify the timeout for each sent HTTP request. The feature remains a Technology Preview.

Previously, Knative services sometimes did not get into the Ready state, reporting waiting for the load balancer to be ready. This issue has been fixed.

Integrating OpenShift Serverless with Red Hat OpenShift Service Mesh causes the net-kourier pod to run out of memory on startup when too many secrets are present on the cluster.

Namespace-scoped brokers might leave ClusterRoleBindings in the user namespace even after deletion of namespace-scoped brokers.

OpenShift Serverless Functions with Quarkus is now GA.

OpenShift Serverless now uses Knative Serving 1.5.

OpenShift Serverless now uses Knative Eventing 1.5.

OpenShift Serverless now uses Kourier 1.5.

OpenShift Serverless now uses Knative (kn) CLI 1.5.

OpenShift Serverless now uses Knative Kafka 1.5.

OpenShift Serverless now uses Knative Operator 1.3.

The kn func CLI plugin now uses func 1.8.1.

Persistent volume claims (PVCs) are now GA. PVCs provide permanent data storage for your Knative services.

The new trigger filters feature is now available as a Developer Preview. It allows users to specify a set of filter expressions, where each expression evaluates to either true or false for each event.

apiVersion: operator.knative.dev/v1beta1
kind: KnativeEventing
...
...
spec:
  config:
    features:
      new-trigger-filters: enabled
...

Knative Operator 1.3 adds the updated v1beta1 version of the API for operator.knative.dev.

apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
...

apiVersion: operator.knative.dev/v1beta1
kind: KnativeEventing
...

Previously, Federal Information Processing Standards (fips) mode was disabled for Kafka broker, Kafka source, and Kafka sink. This has been fixed, and fips mode is now available.

OpenShift Serverless now uses Knative Serving 1.4.

OpenShift Serverless now uses Knative Eventing 1.4.

OpenShift Serverless now uses Kourier 1.4.

OpenShift Serverless now uses Knative (kn) CLI 1.4.

OpenShift Serverless now uses Knative Kafka 1.4.

The kn func CLI plugin now uses func 1.7.0.

Integrated development environment (IDE) plugins for creating and deploying functions are now available for Visual Studio Code and IntelliJ.

Knative Kafka broker is now GA. Knative Kafka broker is a highly performant implementation of the Knative broker API, directly targeting Apache Kafka.

Knative Kafka sink is now GA. A KafkaSink takes a CloudEvent and sends it to an Apache Kafka topic. Events can be specified in either structured or binary content modes.

Enabling TLS for internal traffic is now available as a Technology Preview.

Previously, Knative Serving had an issue where the readiness probe failed if the container was restarted after a liveness probe fail. This issue has been fixed.

The Federal Information Processing Standards (fips) mode is disabled for Kafka broker, Kafka source, and Kafka sink.

The SinkBinding object does not support custom revision names for services.

The Knative Serving Controller pod adds a new informer to watch secrets in the cluster. The informer includes the secrets in the cache, which increases memory consumption of the controller pod.

OpenShift Serverless now uses Knative Serving 1.3.

OpenShift Serverless now uses Knative Eventing 1.3.

OpenShift Serverless now uses Kourier 1.3.

OpenShift Serverless now uses Knative kn CLI 1.3.

OpenShift Serverless now uses Knative Kafka 1.3.

The kn func CLI plugin now uses func 0.24.

Init containers support for Knative services is now generally available (GA).

OpenShift Serverless logic is now available as a Developer Preview. It enables defining declarative workflow models for managing serverless applications.

For OpenShift Container Platform, you can now use the cost management service with OpenShift Serverless.

Integrating OpenShift Serverless with Red Hat OpenShift Service Mesh causes the net-istio-controller pod to run out of memory on startup when too many secrets are present on the cluster.

The OpenShift Serverless Functions Technology Preview now uses Cloud Native Buildpacks by default to build container images.

The Federal Information Processing Standards (fips) mode is disabled for Kafka broker, Kafka source, and Kafka sink.

In OpenShift Serverless 1.23, support for KafkaBindings and the kafka-binding webhook were removed. However, an existing kafkabindings.webhook.kafka.sources.knative.dev MutatingWebhookConfiguration might remain, pointing to the kafka-source-webhook service, which no longer exists.

$ oc delete mutatingwebhookconfiguration kafkabindings.webhook.kafka.sources.knative.dev

OpenShift Serverless now uses Knative Serving 1.2.

OpenShift Serverless now uses Knative Eventing 1.2.

OpenShift Serverless now uses Kourier 1.2.

OpenShift Serverless now uses Knative (kn) CLI 1.2.

OpenShift Serverless now uses Knative Kafka 1.2.

The kn func CLI plugin now uses func 0.24.

It is now possible to use the kafka.eventing.knative.dev/external.topic annotation with the Kafka broker. This annotation makes it possible to use an existing externally managed topic instead of the broker creating its own internal topic.

The kafka-ch-controller and kafka-webhook Kafka components no longer exist. These components have been replaced by the kafka-webhook-eventing component.

The OpenShift Serverless Functions Technology Preview now uses Source-to-Image (S2I) by default to build container images.

The Federal Information Processing Standards (fips) mode is disabled for Kafka broker, Kafka source, and Kafka sink.

If you delete a namespace that includes a Kafka broker, the namespace finalizer may fail to be removed if the broker’s auth.secret.ref.name secret is deleted before the broker.

Running OpenShift Serverless with a large number of Knative services can cause Knative activator pods to run close to their default memory limits of 600MB. These pods might be restarted if memory consumption reaches this limit. Requests and limits for the activator deployment can be configured by modifying the KnativeServing custom resource:

apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
spec:
  deployments:
  - name: activator
    resources:
    - container: activator
      requests:
        cpu: 300m
        memory: 60Mi
      limits:
        cpu: 1000m
        memory: 1000Mi

If you are using Cloud Native Buildpacks as the local build strategy for a function, kn func is unable to automatically start podman or use an SSH tunnel to a remote daemon. The workaround for these issues is to have a Docker or podman daemon already running on the local development computer before deploying a function.

On-cluster function builds currently fail for Quarkus and Golang runtimes. They work correctly for Node, Typescript, Python, and Springboot runtimes.

OpenShift Serverless now uses Knative Serving 1.1.

OpenShift Serverless now uses Knative Eventing 1.1.

OpenShift Serverless now uses Kourier 1.1.

OpenShift Serverless now uses Knative (kn) CLI 1.1.

OpenShift Serverless now uses Knative Kafka 1.1.

The kn func CLI plugin now uses func 0.23.

Init containers support for Knative services is now available as a Technology Preview.

Persistent volume claim (PVC) support for Knative services is now available as a Technology Preview.

The knative-serving, knative-serving-ingress, knative-eventing and knative-kafka system namespaces now have the knative.openshift.io/part-of: "openshift-serverless" label by default.

The Knative Eventing - Kafka Broker/Trigger dashboard has been added, which allows visualizing Kafka broker and trigger metrics in the web console.

The Knative Eventing - KafkaSink dashboard has been added, which allows visualizing KafkaSink metrics in the web console.

The Knative Eventing - Broker/Trigger dashboard is now called Knative Eventing - Channel-based Broker/Trigger.

The knative.openshift.io/part-of: "openshift-serverless" label has substituted the knative.openshift.io/system-namespace label.

Naming style in Knative Serving YAML configuration files changed from camel case (ExampleName) to hyphen style (example-name). Beginning with this release, use the hyphen style notation when creating or editing Knative Serving YAML configuration files.

The Federal Information Processing Standards (fips) mode is disabled for Kafka broker, Kafka source, and Kafka sink.

OpenShift Serverless now uses Knative Serving 1.0

OpenShift Serverless now uses Knative Eventing 1.0.

OpenShift Serverless now uses Kourier 1.0.

OpenShift Serverless now uses Knative (kn) CLI 1.0.

OpenShift Serverless now uses Knative Kafka 1.0.

The kn func CLI plugin now uses func 0.21.

The Kafka sink is now available as a Technology Preview.

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 OpenShift Serverless 1.18.0 release notes, is now deprecated and replaced by the default-external-scheme key. Usage instructions for the key remain the same.

In OpenShift Serverless 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.

In OpenShift Serverless 1.20.0 (func 0.20), TypeScript functions created with the http template failed to deploy on the cluster. This issue is now fixed.

In OpenShift Serverless 1.20.0 (func 0.20), deploying a function using the gcr.io registry failed with an error. This issue is now fixed.

In OpenShift Serverless 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.

In OpenShift Serverless 1.19.0 (func 0.19), some runtimes were unable to build a function by using podman. This issue is now fixed.

Currently, the domain mapping controller cannot process the URI of a broker, which contains a path that is currently not supported.

apiVersion: serving.knative.dev/v1alpha1
kind: DomainMapping
metadata:
  name: <domain-name>
  namespace: knative-eventing
spec:
  ref:
    name: broker-ingress
    kind: Service
    apiVersion: v1

OpenShift Serverless now uses Knative Serving 0.26.

OpenShift Serverless now uses Knative Eventing 0.26.

OpenShift Serverless now uses Kourier 0.26.

OpenShift Serverless now uses Knative (kn) CLI 0.26.

OpenShift Serverless now uses Knative Kafka 0.26.

The kn func CLI plugin now uses func 0.20.

The Kafka broker is now available as a Technology Preview.

The kn event plugin is now available as a Technology Preview.

The --min-scale and --max-scale flags for the kn service create command have been deprecated. Use the --scale-min and --scale-max flags instead.

OpenShift Serverless deploys Knative services with a default address that uses HTTPS. When sending an event to a resource inside the cluster, the sender does not have the cluster certificate authority (CA) configured. This causes event delivery to fail, unless the cluster uses globally accepted certificates.

$ kn event send --to-url https://ce-api.foo.example.com/

$ kn event send --to Service:serving.knative.dev/v1:event-display

The Kafka broker currently does not work on a cluster with Federal Information Processing Standards (fips) mode enabled.

If you create a Springboot function project directory with the kn func create command, subsequent running of the kn func build command fails with this error message:

[analyzer] no stack metadata found at path ''
[analyzer] ERROR: failed to : set API for buildpack 'paketo-buildpacks/ca-certificates@3.0.2': buildpack API version '0.7' is incompatible with the lifecycle

Deploying a function using the gcr.io registry fails with this error message:

Error: failed to get credentials: failed to verify credentials: status code: 404

TypeScript functions created with the http template fail to deploy on the cluster.

buildEnvs: []

buildEnvs:
- name: BP_NODE_RUN_SCRIPTS
  value: build

In func version 0.20, some runtimes might be unable to build a function by using podman. You might see an error message similar to the following:

ERROR: failed to image: error during connect: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/info": EOF

OpenShift Serverless now uses Knative Serving 0.25.

OpenShift Serverless now uses Knative Eventing 0.25.

OpenShift Serverless now uses Kourier 0.25.

OpenShift Serverless now uses Knative (kn) CLI 0.25.

OpenShift Serverless now uses Knative Kafka 0.25.

The kn func CLI plugin now uses func 0.19.

The KafkaBinding API is deprecated in OpenShift Serverless 1.19.0 and will be removed in a future release.

HTTPS redirection is now supported and can be configured either globally for a cluster or per each Knative service.

In previous releases, the Kafka channel dispatcher waited only for the local commit to succeed before responding, which might have caused lost events in the case of an Apache Kafka node failure. The Kafka channel dispatcher now waits for all in-sync replicas to commit before responding.

In func version 0.19, some runtimes might be unable to build a function by using podman. You might see an error message similar to the following:

ERROR: failed to image: error during connect: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/info": EOF

OpenShift Serverless now uses Knative Serving 0.24.0.

OpenShift Serverless now uses Knative Eventing 0.24.0.

OpenShift Serverless now uses Kourier 0.24.0.

OpenShift Serverless now uses Knative (kn) CLI 0.24.0.

OpenShift Serverless now uses Knative Kafka 0.24.7.

The kn func CLI plugin now uses func 0.18.0.

In the upcoming OpenShift Serverless 1.19.0 release, the URL scheme of external routes will default to HTTPS for enhanced security.

...
spec:
  config:
    network:
      defaultExternalScheme: "http"
...

...
spec:
  config:
    network:
      defaultExternalScheme: "https"
...

In the upcoming OpenShift Serverless 1.19.0 release, the default service type by which the Kourier Gateway is exposed will be ClusterIP and not LoadBalancer.

...
spec:
  ingress:
    kourier:
      service-type: LoadBalancer
...

You can now use emptyDir volumes with OpenShift Serverless. See the OpenShift Serverless documentation about Knative Serving for details.

Rust templates are now available when you create a function using kn func.

The prior 1.4 version of Camel-K was not compatible with OpenShift Serverless 1.17.0. The issue in Camel-K has been fixed, and Camel-K version 1.4.1 can be used with OpenShift Serverless 1.17.0.

Previously, if you created a new subscription for a Kafka channel, or a new Kafka source, a delay was possible in the Kafka data plane becoming ready to dispatch messages after the newly created subscription or sink reported a ready status.

Older versions of the Knative kn CLI might use older versions of the Knative Serving and Knative Eventing APIs. For example, version 0.23.2 of the kn CLI uses the v1alpha1 API version.