1.4. Release Notes for Red Hat OpenShift Serverless 1.8.0

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.

spec:
  template:
    metadata:
      annotations:
        queue.sidecar.serving.knative.dev/resourcePercentage: "10" 

spec:
  template:
    metadata:
      annotations:
        queue.sidecar.serving.knative.dev/resourcePercentage: "10" 

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 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

  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.