1.4. Release Notes for Red Hat OpenShift Serverless 1.8.0

1.4.1. New features

OpenShift Serverless now uses Knative Serving 0.14.1.
OpenShift Serverless now uses Knative Serving Operator 0.14.0.
OpenShift Serverless now uses Knative kn CLI 0.14.0.
OpenShift Serverless uses Knative Eventing 0.14.2.
OpenShift Serverless now uses Knative Eventing Operator 0.14.0.
OpenShift Serverless now uses Kourier 0.14.1.

1.4.2. Known issues

Knative Serving has a fixed, minimum CPU request of 25m for the queue-proxy setting. If your cluster has any value set that conflicts with this, for example, if you have set a minimum CPU request for defaultRequest of more than 25m, the Knative service fails to deploy. As a workaround, you can configure the resourcePercentage annotation individually for your Knative services.
Example resourcePercentage configuration
```
spec:
  template:
    metadata:
      annotations:
        queue.sidecar.serving.knative.dev/resourcePercentage: "10" 1
```
1
queue.sidecar.serving.knative.dev/resourcePercentage is the percentage of user container resources to be used for queue-proxy. This can be between a range of 0.1 - 100.
On OpenShift Container Platform 4.5 and newer versions, deploying a Knative service with traffic distribution shows an invalid URL for the general service address in the Developer perspective of the web console.
The correct URL is shown in YAML resources and CLI command outputs.
If you use a ping source with OpenShift Serverless, after you uninstall and delete all other Knative Eventing components, the pingsource-jobrunner Deployment resource is not deleted.
If you delete a sink before you delete the sink binding connected to it, the SinkBinding object deletion might hang.
As a workaround, you can edit the SinkBinding object and remove the finalizer that causes the hanging:
```
  finalizers:
   - sinkbindings.sources.knative.dev
```
The sink binding behavior has changed in OpenShift Serverless 1.8.0, which breaks backwards compatibility.
To use sink binding, cluster administrators must now label the namespace configured in the SinkBinding object with bindings.knative.dev/include:"true".
Resources configured in the SinkBinding object must also be labeled with bindings.knative.dev/include:"true"; however, this task can be completed by any OpenShift Serverless user.
1. As a cluster administrator, you can label the namespace by entering the following command:
```
$ oc label namespace <namespace> bindings.knative.dev/include=true
```
2. Users must manually add a bindings.knative.dev/include=true label to resources.
  For example, to add this label to a CronJob object, add the following lines to the Job resource YAML definition:
```
  jobTemplate:
    metadata:
      labels:
        app: heartbeat-cron
        bindings.knative.dev/include: "true"
```

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

© 2024 Red Hat, Inc.