×

Installing the OpenShift Serverless Operator enables you to install and use Knative Serving, Knative Eventing, and Knative Kafka on a Red Hat OpenShift Service on AWS cluster. The OpenShift Serverless Operator manages Knative custom resource definitions (CRDs) for your cluster and enables you to configure them without directly modifying individual config maps for each component.

Defining cluster size requirements

To install and use OpenShift Serverless, the Red Hat OpenShift Service on AWS cluster must be sized correctly. The total size requirements to run OpenShift Serverless are dependent on the components that are installed and the applications that are deployed, and might vary depending on your deployment.

The following requirements relate only to the pool of worker machines of the Red Hat OpenShift Service on AWS cluster. Control plane nodes are not used for general scheduling and are omitted from the requirements.

By default, each pod requests approximately 400m of CPU, so the minimum requirements are based on this value. Lowering the actual CPU request of applications can increase the number of possible replicas.

If you have high availability (HA) enabled on your cluster, this requires between 0.5 - 1.5 cores and between 200MB - 2GB of memory for each replica of the Knative Serving control plane.

Installing the OpenShift Serverless Operator

You can install the OpenShift Serverless Operator from the OperatorHub by using the Red Hat OpenShift Service on AWS web console. Installing this Operator enables you to install and use Knative components.

Prerequisites
  • You have access to an Red Hat OpenShift Service on AWS account with cluster or dedicated administrator access.

  • You have logged in to the Red Hat OpenShift Service on AWS web console.

Procedure
  1. In the Red Hat OpenShift Service on AWS web console, navigate to the OperatorsOperatorHub page.

  2. Scroll, or type the keyword Serverless into the Filter by keyword box to find the OpenShift Serverless Operator.

  3. Review the information about the Operator and click Install.

  4. On the Install Operator page:

    1. The Installation Mode is All namespaces on the cluster (default). This mode installs the Operator in the default openshift-serverless namespace to watch and be made available to all namespaces in the cluster.

    2. The Installed Namespace is openshift-serverless.

    3. Select the stable channel as the Update Channel. The stable channel will enable installation of the latest stable release of the OpenShift Serverless Operator.

    4. Select Automatic or Manual approval strategy.

  5. Click Install to make the Operator available to the selected namespaces on this Red Hat OpenShift Service on AWS cluster.

  6. From the CatalogOperator Management page, you can monitor the OpenShift Serverless Operator subscription’s installation and upgrade progress.

    1. If you selected a Manual approval strategy, the subscription’s upgrade status will remain Upgrading until you review and approve its install plan. After approving on the Install Plan page, the subscription upgrade status moves to Up to date.

    2. If you selected an Automatic approval strategy, the upgrade status should resolve to Up to date without intervention.

Verification

After the Subscription’s upgrade status is Up to date, select CatalogInstalled Operators to verify that the OpenShift Serverless Operator eventually shows up and its Status ultimately resolves to InstallSucceeded in the relevant namespace.

If it does not:

  1. Switch to the CatalogOperator Management page and inspect the Operator Subscriptions and Install Plans tabs for any failure or errors under Status.

  2. Check the logs in any pods in the openshift-serverless project on the WorkloadsPods page that are reporting issues to troubleshoot further.

If you want to use Red Hat OpenShift distributed tracing with OpenShift Serverless, you must install and configure Red Hat OpenShift distributed tracing before you install Knative Serving or Knative Eventing.

Next steps