10.2. Release Notes for Red Hat OpenShift Serverless Technology Preview 1.4.0
OpenShift Serverless 1.4.0 contains a bad owner reference that causes the Kubernetes Garbage Collector to incorrectly remove the entire Knative control plane, including all of your services. You must install OpenShift Serverless 1.4.1 to fix this issue.
10.2.1. New features
- OpenShift Serverless 1.4.0 is available on OpenShift Container Platform 4.2 and newer versions.
- OpenShift Serverless has been updated to use Knative Serving 0.11.1.
-
OpenShift Serverless has been updated to use Knative Client (
knCLI) 0.11.0. - OpenShift Serverless has been updated to use Knative Serving Operator 0.11.1.
-
The
knCLI is now available for download through the Command Line Tools page in the OpenShift Container Platform web console. The
KnativeServingobject’s API group has changed in this release fromserving.knative.devtooperator.knative.dev. You will need to adjust any of your scripts or applications that rely on the old API group to use the new API group. The OpenShift Serverless installation instructions have been updated to use the new API group.When upgrading from OpenShift Serverless 1.3.0 to 1.4.0, the OpenShift Serverless Operator will create a
KnativeServingcustom resource (CR) in the new API group for you. This CR will be a mirror of theKnativeServingCR in the old group that was used in OpenShift Serverless 1.3.0.If you need to keep using the old group temporarily, you can use the old CR as before. However, this CR is deprecated and will eventually be removed.
Once you have updated references to the new API group, you can remove any older CR versions and use the newly deployed
KnativeServingCR instead. To safely do this without downtime, remove the owner reference from the newly deployedKnativeServingCR using:$ oc edit knativeserving.operator.knative.dev knative-serving -n knative-serving
After the owner reference has been removed, you can safely remove any older CR versions and start using the new one.
重要If a previous version of the CR exists, changes to the new CR will be overwritten by the OpenShift Serverless Operator. While the old CR is still active, all changes need to be made to that CR.
10.2.2. Fixed issues
-
Connecting to a private, cluster local Knative Service from a namespace that was not part of the
knative-serving-ingressService Mesh was failing oni/o timeout. This issue is now fixed. -
The
container_nameandpod_namemetric labels were removed in OpenShift Container Platform 4.3. The documentation has been updated to use the newcontainerandpodmetric labels instead. If you are using metering with Serverless on OpenShift Container Platform 4.3 or later, you must update your Prometheus queries according to the current version of the Serverless metering documentation.
10.2.3. Known issues
Unqualified usage of
knativeservinginoccommands no longer works because of the migration to a new API group. For example, this command will not work:$ oc get knativeserving -n knative-serving
Use the explicit fully-qualified format instead. For example:
$ oc get knativeserving.operator.knative.dev -n knative-serving
- OpenShift Container Platform scale from zero latency causes a delay of approximately 10 seconds when creating pods. This is a current OpenShift Container Platform limitation.
