Chapter 2. Installing the OpenShift Serverless Operator

Procedure

1. In the web console, navigate to the Operators OperatorHub 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 an Update Channel.

      • The stable channel enables installation of the latest stable release of the OpenShift Serverless Operator. The stable channel is the default.
      • To install another version, specify the corresponding stable-x.y channel, for example stable-1.29.
   4. Select the stable channel as the Update Channel. The stable channel will enable installation of the latest stable release of the OpenShift Serverless Operator.
   5. Select Automatic or Manual approval strategy.
5. Click Install to make the Operator available to the selected namespaces on this OpenShift Container Platform cluster.

6. From the Catalog Operator 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.

1. Switch to the Catalog Operator 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 Workloads Pods page that are reporting issues to troubleshoot further.

Procedure

1. Create a YAML file containing Namespace, OperatorGroup, and Subscription objects to subscribe a namespace to the OpenShift Serverless Operator. For example, create the file serverless-subscription.yaml with the following content:

   Example subscription

   ---
   apiVersion: v1
   kind: Namespace
   metadata:
     name: openshift-serverless
   ---
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
     name: serverless-operators
     namespace: openshift-serverless
   spec: {}
   ---
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: serverless-operator
     namespace: openshift-serverless
   spec:
     channel: stable 1
     name: serverless-operator 2
     source: redhat-operators 3
     sourceNamespace: openshift-marketplace 4

   1

   The channel name of the Operator. The stable channel enables installation of the most recent stable version of the OpenShift Serverless Operator. To install another version, specify the corresponding stable-x.y channel, for example stable-1.29.

   2

   The name of the Operator to subscribe to. For the OpenShift Serverless Operator, this is always serverless-operator.

   3

   The name of the CatalogSource that provides the Operator. Use redhat-operators for the default OperatorHub catalog sources.

   4

   The namespace of the CatalogSource. Use openshift-marketplace for the default OperatorHub catalog sources.

2. Create the Subscription object:

   $ oc apply -f serverless-subscription.yaml