Chapter 1. Service Registry Operator quickstart

This chapter explains how to quickly install Service Registry Operator on the command line.

This quickstart example deploys Service Registry using the SQL storage option:

Note

The recommended installation option for production environments is using the OpenShift OperatorHub. The recommended storage option is SQL or Kafka.

1.1. Quickstart Service Registry Operator installation

You can quickly deploy the Service Registry Operator on the command line, without the Operator Lifecycle Manager, by using a downloaded set of installation files and examples.

Prerequisites

Procedure

  1. Create a project for the installation, for example, service-registry: 

    NAMESPACE="service-registry"
oc new-project "$NAMESPACE"

  2. Apply the file located in the install/ folder: 

    cat install/install.yaml | sed "s/apicurio-registry-operator-namespace/$NAMESPACE/g" | oc apply -f -

1.2. Quickstart Service Registry deployment

To create a new Service Registry deployment, use the SQL storage option. This requires an external PostgreSQL storage to be configured as a prerequisite.

Prerequisites

  • Ensure that the Service Registry Operator is already installed.
  • You have a PostgreSQL database reachable from your OpenShift cluster.

Procedure

  1. Create an ApicurioRegistry custom resource (CR), with your database connection configured, for example:

    Example CR for SQL storage

    apiVersion: registry.apicur.io/v1
kind: ApicurioRegistry
metadata:
  name: example-apicurioregistry-sql
spec:
  configuration:
    persistence: "sql"
    sql:
      dataSource:
        url: "jdbc:postgresql://<service name>.<namespace>.svc:5432/<database name>"
        userName: "postgres"
        password: "<password>" # Optional

  2. Create the ApicurioRegistry CR in the same namespace that the Operator is deployed 

    oc project "$NAMESPACE"
oc apply -f ./examples/apicurioregistry_sql_cr.yaml