Getting support

If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at http://access.redhat.com. Through the customer portal, you can:

  • Search or browse through the Red Hat Knowledgebase of technical support articles about Red Hat products

  • Submit a support case to Red Hat Global Support Services (GSS)

  • Access other product documentation

If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Product for the Documentation component. Please provide specific details, such as the section number, guide name, and OpenShift Serverless version so we can easily locate the content.

Knative Eventing is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

Release Notes for Red Hat OpenShift Serverless 1.7.1

New features

  • OpenShift Serverless now uses Knative Serving 0.13.3.

  • OpenShift Serverless now uses Knative Serving Operator 0.13.3.

  • OpenShift Serverless now uses Knative kn CLI 0.13.2.

  • OpenShift Serverless uses Knative Eventing 0.13.0.

  • OpenShift Serverless now uses Knative Eventing Operator 0.13.3.

Fixed issues

  • In OpenShift Serverless 1.7.0, routes were reconciled continuously when this was not required. This bug is fixed in OpenShift Serverless 1.7.1.

Release Notes for Red Hat OpenShift Serverless 1.7.0

New features

  • OpenShift Serverless 1.7.0 is now Generally Available (GA) on Azure Red Hat OpenShift 4.3 and newer versions. In previous versions, OpenShift Serverless was a Technology Preview.

  • OpenShift Serverless now uses Knative Serving 0.13.2.

  • OpenShift Serverless now uses Knative Serving Operator 0.13.2.

  • OpenShift Serverless now uses Knative kn CLI 0.13.2.

  • Knative kn CLI downloads now support disconnected, or restricted network installations.

  • Knative kn CLI libraries are now signed by Red Hat.

  • Knative Eventing is now available as a Technology Preview with OpenShift Serverless. OpenShift Serverless uses Knative Eventing 0.13.2.

Before upgrading to the latest Serverless release, you must remove the community Knative Eventing Operator if you have previously installed it. Having the Knative Eventing Operator installed will prevent you from being able to install the latest Technology Preview version of Knative Eventing that is included with OpenShift Serverless 1.7.0.

  • High availability (HA) is now enabled by default for the autoscaler-hpa, controller, activator , kourier-control, and kourier-gateway components.

    If you have installed a previous version of OpenShift Serverless, after the KnativeServing custom resource (CR) is updated, the deployment will default to a HA configuration with KnativeServing.spec.high-availability.replicas = 2.

    You can disable HA for these components by completing the procedure in the Configuring high availability components documentation.

  • OpenShift Serverless now supports the trustedCA setting in Azure Red Hat OpenShift’s cluster-wide proxy, and is now fully compatible with Azure Red Hat OpenShift’s proxy settings.

  • OpenShift Serverless now supports HTTPS using the wildcard certificate that is registered for Azure Red Hat OpenShift routes. For more information on http and https on Knative Serving, see the documentation on Verifying your serverless application deployment.

Fixed issues

  • In previous versions, requesting KnativeServing custom resources (CRs) without specifying an API group, for example, oc get knativeserving -n knative-serving, occasionally caused errors. This issue is fixed in OpenShift Serverless 1.7.0.

  • In previous versions, the Knative Serving controller was not notified when a new service CA certificate was generated due to service CA certificate rotation. New revisions created after a service CA certificate rotation were failing with the error:

    Revision "foo-1" failed with message: Unable to fetch image "image-registry.openshift-image-registry.svc:5000/eap/eap-app": failed to resolve image to digest: failed to fetch image information: Get https://image-registry.openshift-image-registry.svc:5000/v2/: x509: certificate signed by unknown authority.

    The OpenShift Serverless Operator now restarts the Knative Serving controller whenever a new service CA certificate is generated, which ensures that the controller is always configured to use the current service CA certificate. For more information, see the Azure Red Hat OpenShift documentation on Securing service traffic using service serving certificate secrets under Authentication.

Known issues

  • When upgrading from OpenShift Serverless 1.6.0 to 1.7.0, support for HTTPS requires a change to the format of routes. Knative services created on OpenShift Serverless 1.6.0 are no longer reachable at the old format URLs. You must retrieve the new URL for each service after upgrading OpenShift Serverless. For more information, see the documentation on Upgrading OpenShift Serverless.

  • If you are using Knative Eventing on an Azure cluster, it is possible that the imc-dispatcher pod may not start. This is due to the pod’s default resources settings. As a work-around, you can remove the resources settings.

  • If you have 1000 Knative services on a cluster, and then perform a reinstall or upgrade of Knative Serving, there will be a delay when you create the first new service after KnativeServing becomes Ready.

    3scale-kourier-control reconciles all previous Knative services before processing the creation of a new service, which causes the new service to spend approximately 800 seconds in an IngressNotConfigured or Unknown state before the state will update to Ready.

Release Notes for Red Hat OpenShift Serverless Technology Preview 1.6.0

New features

  • OpenShift Serverless 1.6.0 is available on Azure Red Hat OpenShift 4.3 and newer versions.

  • OpenShift Serverless now uses Knative Serving 0.13.1.

  • OpenShift Serverless now uses Knative kn CLI 0.13.1.

  • OpenShift Serverless now uses Knative Serving Operator 0.13.1.

  • The serving.knative.dev API group has now been fully deprecated and is replaced by the operator.knative.dev API group.

    You must complete the steps that are described in the OpenShift Serverless 1.4.0 release notes, that replace the serving.knative.dev API group with the operator.knative.dev API group, before you can upgrade to the latest version of OpenShift Serverless.

    This change causes commands without a fully qualified APIGroup and kind, such as oc get knativeserving, to become unreliable and not always work correctly.

    After upgrading to OpenShift Serverless 1.6.0, you must remove the old CRD to fix this issue. You can remove the old CRD by entering the following command:

    $ oc delete crd knativeservings.serving.knative.dev
  • The Subscription Update Channel for new OpenShift Serverless releases was updated from techpreview to preview-4.3.

    You must update your channel by following the upgrade documentation to use the latest OpenShift Serverless version.

  • OpenShift Serverless now supports the use of HTTP_PROXY.

  • OpenShift Serverless now supports HTTPS_PROXY cluster-proxy settings.

    This HTTP_PROXY support does not include using custom certificates.

  • The KnativeServing CRD is now hidden from the Developer Catalog by default so that only users with cluster administrator permissions can view it.

  • Parts of the KnativeServing control plane and data plane are now deployed as highly available (HA) by default.

  • Kourier is now actively watched and reconciles changes automatically.

  • OpenShift Serverless now supports use on Azure Red Hat OpenShift nightly builds.

Fixed issues

  • In previous versions, the oc explain command did not work correctly. The structural schema of the KnativeServing CRD was updated in OpenShift Serverless 1.6.0 so that the oc explain command now works correctly.

  • In previous versions, it was possible to create more than one KnativeServing CR. Multiple KnativeServing CRs are now prevented synchronously in OpenShift Serverless 1.6.0. Attempting to create more than one KnativeServing CR now results in an error.

  • In previous versions, OpenShift Serverless was not compatible with Azure Red Hat OpenShift deployments on GCP. This issue was fixed in OpenShift Serverless 1.6.0.

  • In previous releases, the Knative Serving webhook crashed with an out of memory error if the cluster had more than 170 namespaces. This issue was fixed in OpenShift Serverless 1.6.0.

  • In previous releases, OpenShift Serverless did not automatically fix an Azure Red Hat OpenShift route that it created if the route was changed by another component. This issue was fixed in OpenShift Serverless 1.6.0.

  • In previous versions, deleting a KnativeServing CR occasionally caused the system to hang. This issue was fixed in OpenShift Serverless 1.6.0.

  • Due to the ingress migration from Service Mesh to Kourier that occured in OpenShift Serverless 1.5.0, orphaned VirtualServices sometimes remained on the system. In OpenShift Serverless 1.6.0, orphaned VirtualServices are automatically removed.

Known issues

  • In OpenShift Serverless 1.6.0, if a cluster administrator uninstalls OpenShift Serverless by following the uninstall procedure provided in the documentation, the Serverless dropdown is still be visible in the Administrator perspective of the Azure Red Hat OpenShift web console, and the Knative Service resource is still be visible in the Developer perspective of the Azure Red Hat OpenShift web console. Although you can create Knative services by using this option, these Knative services do not work.

    To prevent OpenShift Serverless from being visible in the Azure Red Hat OpenShift web console, the cluster administrator must delete additional CRDs from the deployment after removing the Knative Serving CR.

    Cluster administrators can remove these CRDs by entering the following command:

    $ oc get crd -oname | grep -E '(serving|internal).knative.dev' | xargs oc delete

Release Notes for Red Hat OpenShift Serverless Technology Preview 1.5.0

New features

  • OpenShift Serverless 1.5.0 is available on Azure Red Hat OpenShift 4.3 and newer versions.

  • OpenShift Serverless now uses Knative Serving 0.12.1.

  • OpenShift Serverless now uses Knative kn CLI 0.12.0.

  • OpenShift Serverless now uses Knative Serving Operator 0.12.1.

  • OpenShift Serverless ingress implementation was updated to use Kourier in place of Service Mesh. No user intervention is necessary, as this change is automatic when the OpenShift Serverless Operator is upgraded to 1.5.0.

Fixed issues

  • In previous releases, Azure Red Hat OpenShift scale from zero latency caused a delay of approximately 10 seconds when creating pods. This issue was fixed in the Azure Red Hat OpenShift 4.3.5 bug fix update.

Known issues

  • Deleting KnativeServing.operator.knative.dev from the knative-serving namespace may cause the deletion process to hang. This is due to a race condition between deletion of the CRD and knative-openshift-ingress removing finalizers.

Additional resources

OpenShift Serverless is based on the open source Knative project.