This is a cache of https://docs.openshift.com/container-platform/4.1/applications/service_brokers/installing-template-service-broker.html. It is a snapshot of the page at 2024-12-03T02:59:04.327+0000.
Installing the <strong>template</strong> service Broker - Service brokers | Applications | OpenShift Container Platform 4.1
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Installing the template Service Broker

You can install the template Service Broker to gain access to the template applications that it provides.

The template Service Broker is deprecated in OpenShift Container Platform 4. Equivalent and better functionality is present in the Operator Framework and Operator Lifecycle Manager (OLM).
Prerequisites

About the template Service Broker

The template Service Broker gives the service catalog visibility into the default Instant App and Quickstart templates that have shipped with OpenShift Container Platform since its initial release. The template Service Broker can also make available as a service anything for which an OpenShift Container Platform template has been written, whether provided by Red Hat, a cluster administrator or user, or a third-party vendor.

By default, the template Service Broker shows objects that are globally available from the openshift project. It can also be configured to watch any other project that a cluster administrator chooses.

The template Service Broker is not installed by default in OpenShift Container Platform 4.

Installing the template Service Broker Operator

Prerequisites

  • You have installed the service catalog.

Procedure

The following procedure installs the template Service Broker Operator using the web console.

  1. Create a namespace.

    1. Navigate in the web console to Administration → Namespaces and click Create Namespace.

    2. Enter openshift-template-service-broker in the Name field and click Create.

      The namespace must start with openshift-.

  2. Navigate to the Catalog → OperatorHub page. Verify that the openshift-template-service-broker project is selected.

  3. Select template Service Broker Operator.

  4. Read the information about the Operator and click Install.

  5. Review the default selections and click Subscribe.

Next, you must start the template Service Broker in order to access the template applications it provides.

Starting the template Service Broker

After you have installed the template Service Broker Operator, you can start the template Service Broker using the following procedure.

Prerequisites

  • You have installed the service catalog.

  • You have installed the template Service Broker Operator.

Procedure

  1. Navigate in the web console to Catalog → Installed Operators and select the openshift-template-service-broker project.

  2. Select the template Service Broker Operator.

  3. Under Provided APIs, click Create New for template Service Broker.

  4. Review the default YAML and click Create.

  5. Verify that the template Service Broker has started.

    After the template Service Broker has started, you can view the available template applications by navigating to Catalog → Developer Catalog and selecting the Service Class checkbox. Note that it may take a few minutes for the template Service Broker to start and the template applications to be available.

    If you do not yet see these Service classes, you can check the status of the following items:

    • template Service Broker Pod status

      • From the Workloads → Pods page for the openshift-template-service-broker project, verify that the Pod that starts with apiserver- has a status of Running and readiness of Ready.

    • Cluster service broker status

      • From the Catalog → Broker Management → Service Brokers page, verify that the template-service-broker service broker has a status of Ready.

    • Service catalog controller manager Pod logs

      • From the Workloads → Pods page for the openshift-service-catalog-controller-manager project, review the logs for each of the Pods and verify that you see a log entry with the message Successfully fetched catalog entries from broker.